Closed
Bug 420460
Opened 16 years ago
Closed 16 years ago
[gnomestripe] Vista Aero theme changes broke gnomestripe
Categories
(Firefox :: Theme, defect, P1)
Tracking
()
RESOLVED
FIXED
Firefox 3 beta4
People
(Reporter: wgianopoulos, Assigned: reed)
References
Details
(Keywords: dogfood, regression)
Attachments
(1 file, 3 obsolete files)
15.57 KB,
patch
|
Details | Diff | Splinter Review |
The code checked in to fix bug 419319 changed theme elements which formerly had global definitions to now have separate 'luna' and aero' definitions.
Flags: blocking-firefox3?
Updated•16 years ago
|
Priority: -- → P1
Target Milestone: --- → Firefox 3 beta4
Reporter | ||
Comment 1•16 years ago
|
||
This is just wrong. Having to specify the name of a Windows OS theme in order to override applications defaults in a Linux theme is just not right.
Comment 2•16 years ago
|
||
I still don't understand why that isn't just being backed out. They fixed a minor annoyance to help 3rd party themes (which there aren't that many of) just to break 1st party themes that are constantly being updated
Reporter | ||
Comment 3•16 years ago
|
||
Comment on attachment 306732 [details] [diff] [review] Workaraound Not much of a workaround. It doesn't work.
Attachment #306732 -
Attachment is obsolete: true
Reporter | ||
Comment 4•16 years ago
|
||
This one works. The other one kind of had 'luna' at the wrong point in the path. This one also 'fixes' all 3 jar.mn files.
Reporter | ||
Comment 5•16 years ago
|
||
Comment on attachment 306757 [details] [diff] [review] Workaround V2 This caused another regression. New patch forthcoming.
Attachment #306757 -
Attachment is obsolete: true
Reporter | ||
Comment 6•16 years ago
|
||
I'm not sure why, but applying the same logic in browser resulted in the loss of bookmark icons being displayed.
Comment 7•16 years ago
|
||
I think, fwiw, replacing "luna" with "default" mitigates 90% of the weirdness. The way we package our own themes feels like its pretty broken and limiting, need to figure out how to reswizzle this next cycle so we lose the fairly broken dependencies
Updated•16 years ago
|
Flags: blocking-firefox3? → blocking-firefox3+
Updated•16 years ago
|
Assignee: nobody → rflint
Reporter | ||
Comment 8•16 years ago
|
||
OK. I figured out what i did wrong last time with browser. This fixes all three files.
Attachment #306761 -
Attachment is obsolete: true
Reporter | ||
Comment 9•16 years ago
|
||
(In reply to comment #7) > I think, fwiw, replacing "luna" with "default" mitigates 90% of the weirdness. > The way we package our own themes feels like its pretty broken and limiting, > need to figure out how to reswizzle this next cycle so we lose the fairly > broken dependencies > So, what is the correct course of action here? Check this in and then change 'luna' to default' in all of themes in another bug? Or, should we wait until the 'luna' to default' change and then check in a real fix here?
Assignee | ||
Comment 10•16 years ago
|
||
I have a patch to fix all this in bug 419319.
Assignee: rflint → reed
Assignee | ||
Comment 11•16 years ago
|
||
Fixed by patch in bug 419319.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•