Closed
Bug 504160
Opened 16 years ago
Closed 8 years ago
use proper Toolbar.png regions for the inactive window state
Categories
(Firefox :: Theme, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: mstange, Unassigned)
Details
(Keywords: polish, Whiteboard: [polish-easy][polish-visual])
Attachments
(1 file)
|
14.98 KB,
patch
|
Details | Diff | Splinter Review |
Right now we're using the active images with 70% opacity, which is just wrong.
Also, the glyphs on the inactive toolbar buttons should look disabled at all times as long as the buttons aren't click-through (bug 392188).
| Reporter | ||
Updated•16 years ago
|
Whiteboard: [polish-easy][polish-visual]
Updated•16 years ago
|
Summary: Toolbar.png needs proper images for the inactive window state → use proper Toolbar.png regions for the inactive window state
| Reporter | ||
Updated•16 years ago
|
Assignee: nobody → mstange
Status: NEW → ASSIGNED
| Reporter | ||
Comment 1•16 years ago
|
||
Toolbar.png has been updated in bug 494927.
Stephen, I think we also need an image for the *checked* bookmarks and history buttons in inactive mode.
| Reporter | ||
Comment 2•16 years ago
|
||
Well, maybe we don't need them. Using opacity: 0.7 on the active checked icons looks good, too.
| Reporter | ||
Comment 3•16 years ago
|
||
This patch applies on top of the one in bug 505699. If this gets reviewed first, which is not unlikely, I'll just leave out the parts with the fullscreen and restore buttons when checking this in, and check them in after bug 505699.
In this patch I'm also removing some !importants and replacing them with :not([disabled="true"]).
We have many buttons that don't ever get disabled but where we still set the disabled image region. This probably doesn't make sense but I didn't touch it.
Attachment #394445 -
Flags: review?(dao)
Comment 4•16 years ago
|
||
(In reply to comment #1)
> Toolbar.png has been updated in bug 494927.
Not anymore. I've removed the inactive state in an attempt to avoid the txul issue. We can try to re-add the regions here, or maybe use the ones for the disabled state with a reduced opacity. Looking at attachment 394375 [details], I'm leaning towards the latter.
(In reply to comment #3)
> We have many buttons that don't ever get disabled but where we still set the
> disabled image region. This probably doesn't make sense but I didn't touch it.
Filed bug 510442.
| Reporter | ||
Updated•16 years ago
|
Attachment #394445 -
Flags: review?(dao)
| Reporter | ||
Comment 5•16 years ago
|
||
(In reply to comment #4)
> or maybe use the ones for the disabled state with a reduced opacity. Looking
> at attachment 394375 [details], I'm leaning towards the latter.
When I looked at the image I thought that it might work, too, but in reality it doesn't work at all. For example, with 0.75 opacity (what we're using right now), the border is still much too dark (#7F7F7F at the top and #797979 at the bottom, whereas they should be #A3A3A3 and #9B9B9B).
I'm still trying to figure out how to avoid the Txul hit. The only way to find out is probably to run Txul locally and experiment a little.
| Reporter | ||
Comment 6•16 years ago
|
||
You know what, we could fool Txul by splitting Toolbar.png into two images: one for the buttons that are in the default set, and one for the rest. This might not even be cheating.
Comment 7•16 years ago
|
||
(In reply to comment #6)
> This might not even be cheating.
I think it is, as we expect users to put these buttons on the toolbar.
| Reporter | ||
Updated•16 years ago
|
Assignee: mstange → nobody
Status: ASSIGNED → NEW
| Reporter | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•