Closed
Bug 412307
Opened 18 years ago
Closed 12 years ago
Remove unneeded declarations from gnomestripe
Categories
(Toolkit :: Themes, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: frnchfrgg, Assigned: frnchfrgg)
Details
(Keywords: perf)
Attachments
(1 file, 2 obsolete files)
|
25.77 KB,
patch
|
Details | Diff | Splinter Review |
According to discussion on IRC, whereas winestripe cannot afford to be broken without native theming because of non uxtheme-able Windows, gnomestripe depends on the native theming and doesn't need to be usable without it; a lot of the CSS (borders, backgrounds) is thus unneeded yet costly, so we should clean up gnomestripe.
| Assignee | ||
Updated•18 years ago
|
Version: unspecified → Trunk
| Assignee | ||
Comment 1•18 years ago
|
||
This is a work in progress patch; I'd like people knowing more of the theme structure to say if some things that I removed should be put elsewhere (for other rules that assumed that border/background would be already set).
While doing the cleanup, I noticed that about half of the css files have no border/background set for native themed widgets, and the other half (probably older definitions, or coming from winstripe) needs cleanup.
| Assignee | ||
Comment 2•18 years ago
|
||
Sorry, last patch was garbage (an old ultrabitrotted patch I downloaded about another bug)
Attachment #298601 -
Attachment is obsolete: true
Updated•18 years ago
|
Component: Themes → OS Integration
Keywords: perf
Product: Core → Firefox
QA Contact: themes → os.integration
Comment 3•18 years ago
|
||
Ryan, can you take a look at this?
Updated•18 years ago
|
Assignee: frnchfrgg-mozbugs → nobody
Status: ASSIGNED → NEW
Component: OS Integration → Theme
QA Contact: os.integration → theme
Updated•18 years ago
|
Assignee: nobody → frnchfrgg-mozbugs
Updated•18 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 4•18 years ago
|
||
I dogfooted this patch for a long time without noticing problems, and refrained to remove code if I was too unsure. Maybe there remains some part of the CSS that overrides a -moz-appearance and expect the previous styling to be there to base upon, thus breaking with this patch... I hope this is not the case and I have correctly verified the dependencies...
Attachment #298602 -
Attachment is obsolete: true
Attachment #302218 -
Flags: review?(rflint)
| Assignee | ||
Comment 5•17 years ago
|
||
I conducted a small Txul test with and without the patch, and with 3 runs of standard Txul (only 10 browser windows opened one at a time, the first ignored) with, and 3 without, I found that the performance gains of this patch are pretty much in the noise range, so not that interesting.
I believe that the first window show gains more with this patch, but since there is much more noise for this one it's difficult to say for sure.
I'll try to do more comprehensive tests when I have more time, but the net result seems to be that it's not critical enough to bother checkin in something potentially dangerous this late in the game for so small an effect on performance.
This is still interesting for cleanup sake, but not for 1.9 anyway
Comment 6•16 years ago
|
||
Are you sure this wouldn't break stuff? Somebody could be setting -moz-appearance:none and expect a meaningful fallback styling.
Component: Theme → Themes
Product: Firefox → Toolkit
QA Contact: theme → themes
Updated•16 years ago
|
Attachment #302218 -
Flags: review?(rflint)
Comment 7•12 years ago
|
||
Comment 5 says the wins from this bug were in the noise range, and comment 6 says it might be risk to do these changes, so Wontfix
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•