Community
Participate
Working Groups
It appears that in dark mode, normal background for views and editors is #2F2F2F (decimal 47,47,47), also for views showing trees (package explorer, Git Repositories vies, Outline view). Trees and tables inside Forms appear to use #323538 as background (see for instance PDE's manifest editor, Overview, Execution Environments). In EGit views, I see a number of inconsistencies: Staging View: - Commit message editor has background #323538, would expect #2F2F2F - staged/unstaged #383A3B (56,58,59). Would have expected #323538; History: - Commit table, file tree: #323538 - Commit message viewer/file diff: #404447 (64,68,71); the containing Composite does has #2F2F2F as background (visible between the two text areas). Expected: - All commit message editors or viewers use the normal #2F2F2F background. - All diff viewers use #2F2F2F. - All tables/trees inside forms use the default #323538, otherwise #2F2F2F The general Eclipse theme could maybe consider not using #323538 for trees/tables inside forms, but also #2F2F2F. Otherwise, EGit could consider using #2F2F2F explicitly for the trees/tables in the history and staging views; it'd be more consistent with the package explorer or outline view, where the trees also have #2F2F2F as background.
New Gerrit change created: https://git.eclipse.org/r/c/egit/egit/+/190515
(In reply to Eclipse Genie from comment #1) > New Gerrit change created: https://git.eclipse.org/r/c/egit/egit/+/190515 This fixes the background of the commit message editor in the staging view. I have _no_ idea where the #404447 in the history view, commit message and diff viewer bottom left, comes from. The HyperlinkSourceViewer listens to prefernce changes and does set the background color to #2F2F2F. There must be something else that overrides this, but what? I also don't see where #383A3B for the staged/unstaged trees in the staging view come from. These are trees inside form sections, so I would have expected #323538. @Lars, can you help here?
(In reply to Thomas Wolf from comment #2) > (In reply to Eclipse Genie from comment #1) > > New Gerrit change created: https://git.eclipse.org/r/c/egit/egit/+/190515 > This fixes the background of the commit message editor in the staging view. > > I have _no_ idea where the #404447 in the history view, commit message and > diff viewer bottom left, comes from. The HyperlinkSourceViewer listens to > prefernce changes and does set the background color to #2F2F2F. There must > be something else that overrides this, but what? > > I also don't see where #383A3B for the staged/unstaged trees in the staging > view come from. These are trees inside form sections, so I would have > expected #323538. > > @Lars, can you help here? There is an entry in the e4-dark-drag-styling.css file .MPart Section Tree { background-color: #2F2F2F; color: #DDDDDD; } I opened Bug 578617 to improve the default dark theme settings.
#404447 in the history view comes from e4_dark_partstyle.css, which has .MPart DatePicker, .MPart DatePicker > Text, .MPart ScheduleDatePicker, .MPart ScheduleDatePicker > Text, .MPart CCombo, .MPart Spinner, .MPart Composite > StyledText, .MPart PageBook > SashForm Label, .MPart SashForm > Text[style~='SWT.BORDER'] { background-color: #3f4447; color: #BBBBBB; } (Don't know why on my Mac the red component is 0x40 instead of 0x3f when rendered.) The ".MPart Composite > StyledText" causes this.
New Gerrit change created: https://git.eclipse.org/r/c/egit/egit/+/190525
New Gerrit change created: https://git.eclipse.org/r/c/egit/egit/+/190530
Gerrit change https://git.eclipse.org/r/c/egit/egit/+/190515 was merged to [master]. Commit: http://git.eclipse.org/c/egit/egit.git/commit/?id=040bbfc5c7e8408c47190c56186088de903a3a00
Gerrit change https://git.eclipse.org/r/c/egit/egit/+/190525 was merged to [master]. Commit: http://git.eclipse.org/c/egit/egit.git/commit/?id=4a115a2646ecb562761aa53aeca7d2ca591eb7a3
Gerrit change https://git.eclipse.org/r/c/egit/egit/+/190530 was merged to [master]. Commit: http://git.eclipse.org/c/egit/egit.git/commit/?id=6f925c81d59b9caa35dc8b523907f135f55ab9cf
*** Bug 578758 has been marked as a duplicate of this bug. ***