Closed
Bug 861088
Opened 12 years ago
Closed 12 years ago
Make the subview widgets show their contents as an arrow panel when the widget is not located in the Menu Panel
Categories
(Firefox :: Toolbars and Customization, defect)
Firefox
Toolbars and Customization
Tracking
()
RESOLVED
FIXED
Firefox 28
People
(Reporter: mconley, Assigned: jaws)
References
Details
Attachments
(1 file, 1 obsolete file)
|
10.27 KB,
patch
|
mconley
:
review+
|
Details | Diff | Splinter Review |
Currently, the new History widget doesn't do anything in the nav-bar. One option is to have it open the History side-bar. The other option is to open the Library at the History view.
There are probably other options. We should decide on one and implement it.
Comment 1•12 years ago
|
||
Or show the sub-view in a panel - consistency FTW (and it'd be more contextual than opening a side-bar or the Library). I'd been thinking we should eventually abstract out the sub-views somehow, so this kind of thing is possible.
| Assignee | ||
Updated•12 years ago
|
Assignee: nobody → jaws
Status: NEW → ASSIGNED
| Assignee | ||
Comment 2•12 years ago
|
||
The styling of the panel isn't right, but I think this gets us in the right direction.
Attachment #739150 -
Flags: feedback?(bmcbride)
Comment 3•12 years ago
|
||
Comment on attachment 739150 [details] [diff] [review]
WIP patch
Review of attachment 739150 [details] [diff] [review]:
-----------------------------------------------------------------
Yep, that'd work nicely.
For robustness, might want to add a sanity check for the panel, when opening a subview - ensuring that the node is where we expect it to be (and if it isn't there, move it).
::: browser/base/content/panelUI.js
@@ +221,5 @@
> + characterData: true,
> + childList: true,
> + subtree: true
> + });
> + } else if (aPlacementArea == CustomizableUI.AREA_NAVBAR) {
This shouldn't be checking it's in the navbar, but rather that it's in an area that isn't the panel.
Attachment #739150 -
Flags: feedback?(bmcbride) → feedback+
| Assignee | ||
Comment 4•12 years ago
|
||
This fixes the nits that Blair brought up in the feedback pass and gets the content of the panel to match the styling of the subview.
Attachment #739150 -
Attachment is obsolete: true
Attachment #743296 -
Flags: review?(mconley)
Attachment #743296 -
Flags: review?(bmcbride)
| Assignee | ||
Comment 5•12 years ago
|
||
Also tested it with the Bookmarks widget and it works well.
Summary: Make the History widget do something when it's in the nav-bar → Make the subview widgets show their contents as a panel when in the nav-bar
| Assignee | ||
Updated•12 years ago
|
Summary: Make the subview widgets show their contents as a panel when in the nav-bar → Make the subview widgets show their contents as an arrow panel when the widget is not located in the Menu Panel
| Reporter | ||
Comment 6•12 years ago
|
||
Comment on attachment 743296 [details] [diff] [review]
Patch
Review of attachment 743296 [details] [diff] [review]:
-----------------------------------------------------------------
Looking forward to making use of this in bug 855805. :) Thanks.
::: browser/components/customizableui/content/panelUI.js
@@ +174,5 @@
>
> /**
> * Shows a subview in the panel with a given ID.
> *
> * @param aViewId the ID of the subview to show.
The function documentation should be updated.
::: browser/themes/shared/customizableui/panelUIOverlay.inc.css
@@ +187,5 @@
> display: none;
> }
>
> +#customizationui-widget-panel {
> + max-width: 23em;
If this is supposed to match the menu panel, then this should be @menuPanelWidth@, as opposed to 23em.
Attachment #743296 -
Flags: review?(mconley) → review+
| Assignee | ||
Comment 7•12 years ago
|
||
Whiteboard: [fixed in jamun]
| Assignee | ||
Updated•12 years ago
|
Attachment #743296 -
Flags: review?(bmcbride)
| Reporter | ||
Comment 8•12 years ago
|
||
Whiteboard: [fixed in jamun] → [fixed in jamun][fixed-in-ux]
Comment 9•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [fixed in jamun][fixed-in-ux]
Target Milestone: --- → Firefox 28
You need to log in
before you can comment on or make changes to this bug.
Description
•