Closed
Bug 429580
Opened 17 years ago
Closed 17 years ago
Remove CSS that displays throbbers 50% transparent
Categories
(Firefox :: Theme, defect)
Firefox
Theme
Tracking
()
RESOLVED
FIXED
Firefox 3
People
(Reporter: Dolske, Assigned: Dolske)
References
Details
Attachments
(1 file)
5.65 KB,
patch
|
beltzner
:
ui-review+
beltzner
:
approval1.9+
|
Details | Diff | Splinter Review |
After landing the updated throbber from bug 326817 and looking at it in a nightly, I noticed it looks much fainter than it should be. Loading chrome://global/skin/icons/loading_16.png looks fine though.
I took a look at the CSS, and noticed that we're actually showing the throbbers at 50% opacity. The entries have been in winstripe since browser.css was created, and gnomestripe carried them over. Not sure why they were originally added, but I'd guess it was a hack to make the throbber more subtle.
Pinstripe currently displays the images at full opacity.
The updated winstripe/gnomestripe throbbers were both designed and reviewed using HTML mockups (full opacity against different background), so they should be expected to look fine at full opacity. [And faint at 50% opacity, as is the case.]
Attachment #316313 -
Flags: ui-review?(beltzner)
Attachment #316313 -
Flags: approval1.9?
Assignee | ||
Comment 1•17 years ago
|
||
Note to self: I also looked at the throbber CSS waiting to be updated by bug 428764, and verified those are already at full opacity.
Comment 2•17 years ago
|
||
Comment on attachment 316313 [details] [diff] [review]
Patch v.1
uir+a=beltzner
Attachment #316313 -
Flags: ui-review?(beltzner)
Attachment #316313 -
Flags: ui-review+
Attachment #316313 -
Flags: approval1.9?
Attachment #316313 -
Flags: approval1.9+
Assignee | ||
Comment 3•17 years ago
|
||
Checking in browser/themes/gnomestripe/browser/browser.css;
new revision: 1.210; previous revision: 1.209
Checking in browser/themes/winstripe/browser/browser.css;
new revision: 1.203; previous revision: 1.202
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•