Closed
Bug 885066
Opened 11 years ago
Closed 11 years ago
lightweight themes should not get applied to windows already in customization mode
Categories
(Firefox :: Toolbars and Customization, defect)
Firefox
Toolbars and Customization
Tracking
()
RESOLVED
FIXED
Firefox 28
People
(Reporter: jaws, Assigned: Gijs)
References
(Blocks 1 open bug)
Details
(Whiteboard: [Australis:M9][see comment #3][Australis:P4])
Attachments
(2 files, 1 obsolete file)
5.25 KB,
patch
|
Unfocused
:
review+
|
Details | Diff | Splinter Review |
4.71 KB,
patch
|
Unfocused
:
review+
|
Details | Diff | Splinter Review |
lightweight theme applied in customization mode this should have been fixed by https://bugzilla.mozilla.org/show_bug.cgi?id=870602 but maybe it doesn't work on XP or the build that was used to test was too old. needs to be verified.
Reporter | ||
Comment 1•11 years ago
|
||
from ui-review etherpad, this is because the harness applied the LWT after entering (see the order in the filename). The problem shouldn't occur when run with the order reversed. Note that this would be a problem if we ever allow customizing LWT from within customization mode.
Comment 2•11 years ago
|
||
Yeah, that was my comment. The arguments to mozscreenshot were not in the right order to match how a user would hit this unless we allow enabling LWT from customization mode in the future. Probably fine to WONTFIX for now and remember to put "LightweighTheme" before "CustomizeMode" when using mozscreenshots.
Status: NEW → UNCONFIRMED
Ever confirmed: false
Comment 3•11 years ago
|
||
(In reply to Matthew N. [:MattN] from comment #2) > Yeah, that was my comment. The arguments to mozscreenshot were not in the > right order to match how a user would hit this unless we allow enabling LWT > from customization mode in the future. It's quite easy to do manually if you have multiple windows.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 4•11 years ago
|
||
Hm, this lightweight theme business looks like it's going to add quite a bit of complexity and ugliness in various parts. Is there a pre-existing way to disable lwthemes on a per-window basis?
OS: Windows XP → All
Hardware: x86_64 → All
Summary: lightweight theme applied in customization mode on Windows XP → lightweight themes should not get applied to windows already in customization mode
Whiteboard: [Australis:M?] → [Australis:M?][see comment #3]
Updated•11 years ago
|
Whiteboard: [Australis:M?][see comment #3] → [Australis:M?][see comment #3][Australis:P4]
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Comment 7•11 years ago
|
||
(In reply to Jared Wein [:jaws] from comment #1) > Note that this would be a problem if we ever allow customizing LWT from > within customization mode. If/when we ever do that, I think we'll need to figure out how to best *show* the LWT.
Comment 8•11 years ago
|
||
(In reply to Dão Gottwald [:dao] from comment #3) > It's quite easy to do manually if you have multiple windows. Hm, this brings up an important issue: If you do something that would trigger this bug, and we fix this bug, then suddenly you're left with enabling a lightweight theme and it will look like it's not working in any window. So, in light of that, I think bug 879994 should really have been a change to LightweightThemeConsumer - so it can be disabled per-window (à la comment 4). Would you mind making that change here too? Will need to port bug 870602 too, to use LightweightThemeConsumer (document.documentElement._lightweightTheme).
Comment 9•11 years ago
|
||
Comment on attachment 819755 [details] [diff] [review] don't apply LWTs to windows already in customization mode, Review of attachment 819755 [details] [diff] [review]: ----------------------------------------------------------------- As per comment 8.
Attachment #819755 -
Flags: review?(bmcbride) → review-
Assignee | ||
Comment 10•11 years ago
|
||
Alright, this keeps the LWT in the other windows. I'll do a straight backout of the temporary toggle thing (including its test) in a separate patch in a second.
Attachment #820257 -
Flags: review?(bmcbride)
Assignee | ||
Updated•11 years ago
|
Attachment #819755 -
Attachment is obsolete: true
Updated•11 years ago
|
Attachment #820260 -
Flags: review?(bmcbride) → review+
Updated•11 years ago
|
Attachment #820257 -
Flags: review?(bmcbride) → review+
Assignee | ||
Comment 12•11 years ago
|
||
https://hg.mozilla.org/projects/ux/rev/81ef9027114f
Whiteboard: [Australis:M?][see comment #3][Australis:P4] → [Australis:M9][see comment #3][Australis:P4][fixed-in-ux]
Assignee | ||
Comment 13•11 years ago
|
||
(In reply to :Gijs Kruitbosch from comment #12) > https://hg.mozilla.org/projects/ux/rev/81ef9027114f Uh, so that was the backout. The patch itself went in as https://hg.mozilla.org/projects/ux/rev/f4ec7c4100e2 . I blame mcMerge not dealing with this correctly for bugspam.
Assignee | ||
Comment 14•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/f4ec7c4100e2
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [Australis:M9][see comment #3][Australis:P4][fixed-in-ux] → [Australis:M9][see comment #3][Australis:P4]
Target Milestone: --- → Firefox 28
You need to log in
before you can comment on or make changes to this bug.
Description
•