Closed
Bug 1003588
Opened 11 years ago
Closed 11 years ago
Separator in customize menu creates a blank (and unremovable) space
Categories
(Firefox :: Toolbars and Customization, defect)
Tracking
()
VERIFIED
FIXED
Firefox 32
People
(Reporter: bugs, Assigned: Gijs)
References
Details
Attachments
(2 files)
56.86 KB,
image/png
|
Details | |
9.56 KB,
patch
|
jaws
:
review+
Sylvestre
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140428194004
Steps to reproduce:
Move a separator from the navigation bar to the menu that opens when you hit the menu button (the one with the three-lines as an icon).
Actual results:
It created a blank space, offset the line, and now cannot be moved.
See attached picture: the separator is to the right of the home button.
Expected results:
Since adding a separator to the navigation bar no longer seems possible (I think?), I'm not really sure. I suppose the separator should be visible, not just show a blank space, and it certainly should be movable.
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(gijskruitbosch+bugs)
Comment 1•11 years ago
|
||
Confirm this still exists in F29 final release.
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0
Build ID: 20140428120048
Comment 2•11 years ago
|
||
Marking new based on comment 1.
Status: UNCONFIRMED → NEW
Component: Untriaged → Toolbars and Customization
Ever confirmed: true
Updated•11 years ago
|
Flags: firefox-backlog+
Assignee | ||
Comment 3•11 years ago
|
||
Unfortunately, I don't think making these items behave well in the menupanel is something that we should spend a significant amount of time on. Instead, I think we should just not let people move them there; they're only really useful in toolbars.
Attachment #8420342 -
Flags: review?(jaws)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(gijskruitbosch+bugs)
Comment 4•11 years ago
|
||
Comment on attachment 8420342 [details] [diff] [review]
don't let spacers, springs and separators go into the panel,
I can't reproduce this bug pre-patch. I used DOM Inspector to add a <xul:toolbarseparator> to the #nav-bar. I then entered customization mode, but I can't drag the separator anywhere.
Aibara, do you see the normal drag icon when hovering over a separator in your toolbar?
Attachment #8420342 -
Flags: review?(jaws)
Flags: needinfo?(cranberrydoughan)
Comment 5•11 years ago
|
||
Comment on attachment 8420342 [details] [diff] [review]
don't let spacers, springs and separators go into the panel,
In my reproduction attempts I was adding the separator without making it removable, nor tracked by CustomizableUI.
This patch works find. Thanks!
Attachment #8420342 -
Flags: review+
Flags: needinfo?(cranberrydoughan)
Assignee | ||
Comment 6•11 years ago
|
||
Flags: in-testsuite+
Whiteboard: [fixed-in-fx-team]
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 32
Assignee | ||
Comment 8•11 years ago
|
||
Comment on attachment 8420342 [details] [diff] [review]
don't let spacers, springs and separators go into the panel,
[Approval Request Comment]
Bug caused by (feature/regressing bug #): N/A
User impact if declined: Users can put spacers/springs/separators in the menu panel, and not remove them
Testing completed (on m-c, etc.): local, on m-c, has automated test
Risk to taking this patch (and alternatives if risky): medium to low. I don't expect anything to break here, but equally I don't think the severity * frequency of this is high enough to warrant the risk to uplift to beta in the last 3 weeks of the cycle.
String or IDL/UUID changes made by this patch: none
Attachment #8420342 -
Flags: approval-mozilla-aurora?
Updated•11 years ago
|
status-firefox31:
--- → affected
status-firefox32:
--- → fixed
Updated•11 years ago
|
Attachment #8420342 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment 9•11 years ago
|
||
Mozilla/5.0 (X11; Linux i686; rv:30.0) Gecko/20100101 Firefox/30.0
The user is no longer able to place separators inside the Menu panel on latest Nightly, build ID: 20140514030203.
Marking issue verified.
Status: RESOLVED → VERIFIED
Comment 10•11 years ago
|
||
Mozilla/5.0 (X11; Linux i686; rv:32.0) Gecko/20100101 Firefox/32.0
Oups, wrong User Agent pasted above.
Comment 11•11 years ago
|
||
Comment 12•11 years ago
|
||
For anyone hitting this now, you can remove the separator manually:
* Stop Firefox
* Edit the file: ~/.mozilla/firefox/<profile directory>/prefs.js
* Find the line which starts: user_pref("browser.uiCustomization.state"
* Remove the item: \"customizableui-special-separator2\",
* Start Firefox
Comment 13•11 years ago
|
||
This causes a problem for several extensions that add support for "special widgets" to be added to (among other places) the menu panel.
Including:
Classic Theme Restorer
The Puzzle Piece
And mine, The Addon Bar (Restored).
I have worked around it in the current beta version, (source here: https://addons.mozilla.org/en-US/firefox/files/browse/260456/file/modules/spacers.js#top), but it is quite hackish.
Could we add a way to let addons add this functionality cleanly?
Comment 14•11 years ago
|
||
(In reply to GiTcode from comment #13)
> This causes a problem for several extensions that add support for "special
> widgets" to be added to (among other places) the menu panel.
>
> Including:
> Classic Theme Restorer
> The Puzzle Piece
> And mine, The Addon Bar (Restored).
> I have worked around it in the current beta version, (source here:
> https://addons.mozilla.org/en-US/firefox/files/browse/260456/file/modules/
> spacers.js#top), but it is quite hackish.
>
> Could we add a way to let addons add this functionality cleanly?
Not really. The basic premise behind these add-ons adding capabilities that aren't supported by default means that these add-ons should go the full distance and also add the necessary CSS/styling to make placements in these areas look nice and fit in.
Comment 15•11 years ago
|
||
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #14)
> Not really. The basic premise behind these add-ons adding capabilities that
> aren't supported by default means that these add-ons should go the full
> distance and also add the necessary CSS/styling to make placements in these
> areas look nice and fit in.
Right, I agree that the addons should add the proper styling and such to make them fit in, but I was referring to the (as of this bug landing) great difficulty in getting the special widgets into the menu in the first place.
Perhaps we could add a simple switch that an addon could use to let the browser know that special widgets can be in the menu. Then on disable or uninstall the addon could turn the switch back off.
You need to log in
before you can comment on or make changes to this bug.
Description
•