Closed
Bug 461366
Opened 16 years ago
Closed 16 years ago
Don't use -moz-appearance for browser window background, it's not shown anyway
Categories
(Firefox :: Theme, defect)
Tracking
()
RESOLVED
FIXED
Firefox 3.6a1
People
(Reporter: mstange, Assigned: mstange)
Details
(Keywords: perf)
Attachments
(1 file)
(deleted),
patch
|
Gavin
:
review+
|
Details | Diff | Splinter Review |
This might improve drawing performance a little.
Usually the browser background is covered completely by toolbox / tabbrowser / statusbar etc, but when you look at it with QuartzDebug you can see that it's still drawn. A plain background color should be a little faster to draw.
Attachment #344487 -
Flags: review?(gavin.sharp)
Comment 1•16 years ago
|
||
Do we need the background-color at all?
You made the opposite change in bug 431831, do you remember why?
Assignee | ||
Comment 2•16 years ago
|
||
(In reply to comment #1)
> Do we need the background-color at all?
When extensions are involved it's possible that the background-color shows (e.g. behind the Download Statusbar), so I think it makes sense to specify something sane instead of the default white. I don't think it will cost anything.
> You made the opposite change in bug 431831, do you remember why?
Oh, interesting. I hadn't really looked at that patch when I submitted it; it was mostly Kevin's work. I don't know why Kevin chose to make that change.
Comment 3•16 years ago
|
||
Comment on attachment 344487 [details] [diff] [review]
patch v1
OK, I guess we can just take this on trunk. I'd be wary of taking it on branch at this point though.
Attachment #344487 -
Flags: review?(gavin.sharp) → review+
Assignee | ||
Comment 4•16 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.2a1
Comment 5•16 years ago
|
||
(In reply to comment #1)
> Do we need the background-color at all?
Do you want to trigger translucency ;-)
Assignee | ||
Comment 6•16 years ago
|
||
Mh, apparently the change didn't have any effect on Txul perf.
You need to log in
before you can comment on or make changes to this bug.
Description
•