Closed Bug 907376 Opened 11 years ago Closed 11 years ago

Disable the Exit button when in Customization mode

Categories

(Firefox :: Toolbars and Customization, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 28

People

(Reporter: mikedeboer, Assigned: mikedeboer)

References

(Blocks 1 open bug)

Details

(Whiteboard: [Australis:M?][Australis:P3])

Attachments

(2 files)

Since bug 871203 landed, we have an Exit button in the panel. When in Customization Mode, this button might appear to (falsely) suggest it'll take you out of that mode, while instead it will close the browser. To circumvent misinterpretations of this feature and remedy confusion, the exit button should be disabled.
Attachment #793071 - Flags: review?(jaws) → review+
Whiteboard: [Australis:M?][Australis:P3] → [Australis:M?][Australis:P3][fixed-in-ux]
Flags: needinfo?(mdeboer)
Forgot to add this rule. Jared, thanks for finding that! /me slaps himself for missing this
Attachment #793417 - Flags: review?(gijskruitbosch+bugs)
Flags: needinfo?(mdeboer)
Comment on attachment 793417 [details] [diff] [review] Patch v2.1: add opacity rule for disabled Exit button Review of attachment 793417 [details] [diff] [review]: ----------------------------------------------------------------- r=me
Attachment #793417 - Flags: review?(gijskruitbosch+bugs) → review+
(In reply to :Gijs Kruitbosch from comment #5) > Comment on attachment 793417 [details] [diff] [review] > Patch v2.1: add opacity rule for disabled Exit button > > Review of attachment 793417 [details] [diff] [review]: > ----------------------------------------------------------------- > > r=me Actually, nit: please add the rule above the existing one so as not to break blame.
FTFM (In reply to :Gijs Kruitbosch from comment #6) > Actually, nit: please add the *selector* above the existing one so as not to break > blame.
I can't (In reply to :Gijs Kruitbosch from comment #6) > Actually, nit: please add the rule above the existing one so as not to break > blame. I can't do that. I've never heard of rule that should break code-consistency over supporting lack of intelligence in tooling. #PanelUI-help is ALWAYS above #PanelUI-quit in that file, so to break that consistency for the sake of tooling is not gonna fly. As a side note, blame is preserved in VCS revision history. In the current toolchain (like hg.mozilla.org code browser, annotation view), it's a couple of clicks extra to check out the parent revision and blame from there. It might be less convenient.
(In reply to Mike de Boer [:mikedeboer] from comment #8) > I can't (In reply to :Gijs Kruitbosch from comment #6) > > Actually, nit: please add the rule above the existing one so as not to break > > blame. > > I can't do that. I've never heard of rule that should break code-consistency > over supporting lack of intelligence in tooling. #PanelUI-help is ALWAYS > above #PanelUI-quit in that file, so to break that consistency for the sake > of tooling is not gonna fly. Well, I couldn't really see that from the patch context. I also don't think that consistency is particularly important, but I can't bring myself to care much either way. Land it whichever way around you think is best.
(In reply to :Gijs Kruitbosch from comment #9) > Well, I couldn't really see that from the patch context. I also don't think > that consistency is particularly important, but I can't bring myself to care > much either way. Land it whichever way around you think is best. Okido, thanks!
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [Australis:M?][Australis:P3][fixed-in-ux] → [Australis:M?][Australis:P3]
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: