Closed Bug 939489 Opened 11 years ago Closed 11 years ago

CustomizeMode should null-check documentElement._lightweightTheme

Categories

(Firefox :: Toolbars and Customization, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 28

People

(Reporter: Unfocused, Assigned: Unfocused)

References

(Blocks 1 open bug)

Details

(Whiteboard: [Australis:P2][Australis:M9])

Attachments

(1 file)

Seems documentElement._lightweightTheme can be null, if an add-on sets lightweightthemes=false on the <window>. Easy fix to avoid breakage is to just add a null-check when we try to use this in CustomizeMode.jsm.
Attached patch Patch v1Splinter Review
Attachment #833397 - Flags: review?(mconley)
Whiteboard: [Australis:P?][Australis:M?]
Comment on attachment 833397 [details] [diff] [review]
Patch v1

Review of attachment 833397 [details] [diff] [review]:
-----------------------------------------------------------------

Nice and defensive. Thanks Blair!
Attachment #833397 - Flags: review?(mconley) → review+
I wonder if we should make the catch blocks in customization enter/exit display some kind of message if something borked when entering/exiting. Pretty bad UI breakage if any of it breaks, tbh.
(In reply to :Gijs Kruitbosch from comment #3)
> I wonder if we should make the catch blocks in customization enter/exit
> display some kind of message if something borked when entering/exiting.
> Pretty bad UI breakage if any of it breaks, tbh.

Possibly... but that would also mean we're *far* less likely to found out about issues, which IMO is more important at this stage.
https://hg.mozilla.org/projects/ux/rev/9f997c45050c
Whiteboard: [Australis:P?][Australis:M?] → [Australis:P?][Australis:M?][fixed-in-ux]
(In reply to Blair McBride [:Unfocused] from comment #4)
> (In reply to :Gijs Kruitbosch from comment #3)
> > I wonder if we should make the catch blocks in customization enter/exit
> > display some kind of message if something borked when entering/exiting.
> > Pretty bad UI breakage if any of it breaks, tbh.
> 
> Possibly... but that would also mean we're *far* less likely to found out
> about issues, which IMO is more important at this stage.

To be clear, I would put something like "Uh-oh, opening customization mode failed with the following error: ... please report this here: [custom bugzilla link]." but I see your point, I guess.
https://hg.mozilla.org/mozilla-central/rev/9f997c45050c
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [Australis:P?][Australis:M?][fixed-in-ux] → [Australis:P2][Australis:M9]
Target Milestone: --- → Firefox 28
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: