Closed
Bug 1270990
Opened 9 years ago
Closed 9 years ago
Dark theme refresh issues
Categories
(DevTools :: Framework, defect, P1)
DevTools
Framework
Tracking
(firefox48 unaffected, firefox49 verified)
VERIFIED
FIXED
Firefox 49
| Tracking | Status | |
|---|---|---|
| firefox48 | --- | unaffected |
| firefox49 | --- | verified |
People
(Reporter: ntim, Assigned: hholmes)
References
Details
Attachments
(3 files, 2 obsolete files)
|
359.24 KB,
image/png
|
Details | |
|
48.38 KB,
image/png
|
Details | |
|
6.06 KB,
patch
|
bgrins
:
review+
hholmes
:
ui-review+
|
Details | Diff | Splinter Review |
Here are the issues I've found:
- the tabbar has a 2px bottom border
- the debugger toolbar has 2 different bottom border colors
- the icon highlighted state (debugger paused, memory/perf active) doesn't match the tab top border
| Reporter | ||
Comment 1•9 years ago
|
||
Comment 2•9 years ago
|
||
P1, since these were introduced in 49
| Assignee | ||
Updated•9 years ago
|
Assignee: nobody → hholmes
| Assignee | ||
Comment 3•9 years ago
|
||
Attachment #8750308 -
Flags: ui-review?(ntim.bugs)
Attachment #8750308 -
Flags: review?(bgrinstead)
Comment 4•9 years ago
|
||
Comment on attachment 8750308 [details] [diff] [review]
dark-theme-issues.patch
Review of attachment 8750308 [details] [diff] [review]:
-----------------------------------------------------------------
Code changes work for me, but please wait for Tim's confirmation that this fixes all issues before landing
Attachment #8750308 -
Flags: review?(bgrinstead) → review+
| Assignee | ||
Comment 5•9 years ago
|
||
Oh no, sorry—one last small code change brought up in bug 1079135.
Attachment #8750308 -
Attachment is obsolete: true
Attachment #8750308 -
Flags: ui-review?(ntim.bugs)
Attachment #8750388 -
Flags: ui-review?(ntim.bugs)
Attachment #8750388 -
Flags: review?(bgrinstead)
| Reporter | ||
Comment 7•9 years ago
|
||
Comment on attachment 8750388 [details] [diff] [review]
dark-theme-issues.patch
Review of attachment 8750388 [details] [diff] [review]:
-----------------------------------------------------------------
Looks like tool-memory-active.svg hasn't been updated with the new green colour.
But otherwise, looks good to me! Thanks !
Attachment #8750388 -
Flags: ui-review?(ntim.bugs) → ui-review+
| Reporter | ||
Comment 8•9 years ago
|
||
Comment on attachment 8750388 [details] [diff] [review]
dark-theme-issues.patch
Review of attachment 8750388 [details] [diff] [review]:
-----------------------------------------------------------------
::: devtools/client/themes/variables.css
@@ +73,4 @@
> --theme-tab-toolbar-background: #272b35;
> --theme-toolbar-background: #272b35;
> --theme-selection-background: #5675B9;
> + --theme-selection-background-semitransparent: rgba(23, 51, 71, 0.5);
This change makes the selection background much much less obvious.
It's hard to see when the console buttons are checked now.
Perhaps we could find a middle-ground colour between the old and this one ?
Updated•9 years ago
|
Status: NEW → ASSIGNED
Comment 9•9 years ago
|
||
Comment on attachment 8750388 [details] [diff] [review]
dark-theme-issues.patch
Review of attachment 8750388 [details] [diff] [review]:
-----------------------------------------------------------------
::: devtools/client/themes/variables.css
@@ +73,4 @@
> --theme-tab-toolbar-background: #272b35;
> --theme-toolbar-background: #272b35;
> --theme-selection-background: #5675B9;
> + --theme-selection-background-semitransparent: rgba(23, 51, 71, 0.5);
What is the reason for this change?
Just FWIW, the original intent for the difference between --theme-selection-background and --theme-selection-background-semitransparent was that the latter would have the same RGB values but with some alpha applied
| Assignee | ||
Comment 10•9 years ago
|
||
(In reply to Brian Grinstead [:bgrins] from comment #9)
> ::: devtools/client/themes/variables.css
> @@ +73,4 @@
> > --theme-tab-toolbar-background: #272b35;
> > --theme-toolbar-background: #272b35;
> > --theme-selection-background: #5675B9;
> > + --theme-selection-background-semitransparent: rgba(23, 51, 71, 0.5);
>
> What is the reason for this change?
A combo of things. One was that I realized I hadn't captured part of my original designs, so I couldn't argue that the semi-transparent we were using passed AA: http://cl.ly/343f0O0F1W1Z
The second was getting ni?'d on a (old) bug that addressed text and contrast on the old theme, which made me realize the error: bug 1079135
> Just FWIW, the original intent for the difference between
> --theme-selection-background and
> --theme-selection-background-semitransparent was that the latter would have
> the same RGB values but with some alpha applied
Should I go about and rename the variable then, do you think, knowing the above?
Comment 11•9 years ago
|
||
(In reply to Helen V. Holmes (:helenvholmes) (:✨)(pls ni?) from comment #10)
> (In reply to Brian Grinstead [:bgrins] from comment #9)
> > ::: devtools/client/themes/variables.css
> > @@ +73,4 @@
> > > --theme-tab-toolbar-background: #272b35;
> > > --theme-toolbar-background: #272b35;
> > > --theme-selection-background: #5675B9;
> > > + --theme-selection-background-semitransparent: rgba(23, 51, 71, 0.5);
> >
> > What is the reason for this change?
> A combo of things. One was that I realized I hadn't captured part of my
> original designs, so I couldn't argue that the semi-transparent we were
> using passed AA: http://cl.ly/343f0O0F1W1Z
>
> The second was getting ni?'d on a (old) bug that addressed text and contrast
> on the old theme, which made me realize the error: bug 1079135
According to Tim's comment 8, the new color is less obvious. In particular with the console buttons, so please take a look at those before marking for checkin. I'm fine either way if you want to tweak the alpha value of the current RGB to get better text contrast or use this new color.
> > Just FWIW, the original intent for the difference between
> > --theme-selection-background and
> > --theme-selection-background-semitransparent was that the latter would have
> > the same RGB values but with some alpha applied
>
> Should I go about and rename the variable then, do you think, knowing the
> above?
No, I wouldn't rename it either way.
| Assignee | ||
Comment 13•9 years ago
|
||
Copying some issues discussed over IRC and in bug 1271054:
- The contrast between the white and purple colors in the syntax highlighting might need to be revisited.
- The red and green both have really high contrast to the point of being a little glaring.
Comment 14•9 years ago
|
||
Comment on attachment 8750388 [details] [diff] [review]
dark-theme-issues.patch
Review of attachment 8750388 [details] [diff] [review]:
-----------------------------------------------------------------
Clearing review based on Comments 11 and 13
Attachment #8750388 -
Flags: review?(bgrinstead)
| Assignee | ||
Comment 15•9 years ago
|
||
Rolled back the semi-transparent change and updated the active color for the memory tool.
Brian, re: comment 13; would you mind if we addressed those in a separate bug? I think I want to use the devtools in dark theme for a week or so before adjusting it (I'm not sure if it's just the newness that makes me want to change it again so quickly or what.)
Attachment #8750388 -
Attachment is obsolete: true
Attachment #8752191 -
Flags: ui-review+
Attachment #8752191 -
Flags: review?(bgrinstead)
Updated•9 years ago
|
Attachment #8752191 -
Flags: review?(bgrinstead) → review+
Comment 16•9 years ago
|
||
(In reply to Helen V. Holmes (:helenvholmes) (:✨)(pls ni?) from comment #15)
> Brian, re: comment 13; would you mind if we addressed those in a separate
> bug? I think I want to use the devtools in dark theme for a week or so
> before adjusting it (I'm not sure if it's just the newness that makes me
> want to change it again so quickly or what.)
Works for me, but can you please file a follow up for tweaking the colors? If you ultimately decide to not change them we can wontfix it, but at least that way the things in Comment 13 will be tracked.
| Assignee | ||
Comment 17•9 years ago
|
||
See Bug 1273130.
| Assignee | ||
Updated•9 years ago
|
Keywords: checkin-needed
Comment 18•9 years ago
|
||
Keywords: checkin-needed
Comment 19•9 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 49
Comment 20•9 years ago
|
||
I have reproduced this bug with Firefox Nightly 49.0a1 (2016-05-06) on windows 8.1 , 64 bit
The bug's fix is verified on Aurora 49.0a2
Build ID : 20160709004037
User Agent : Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:49.0) Gecko/20100101 Firefox/49.0
[bugday-20160713]
| Reporter | ||
Updated•9 years ago
|
Status: RESOLVED → VERIFIED
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•