Closed
Bug 868135
Opened 11 years ago
Closed 11 years ago
Remove the History sidebar control as a toolbar customization item
Categories
(Firefox :: Toolbars and Customization, defect)
Firefox
Toolbars and Customization
Tracking
()
RESOLVED
FIXED
Firefox 28
People
(Reporter: jaws, Assigned: mconley)
References
(Blocks 1 open bug)
Details
(Whiteboard: [Australis:M6])
Attachments
(1 file)
7.41 KB,
patch
|
jaws
:
review+
|
Details | Diff | Splinter Review |
With Australis, we will now have quite a few history-related items in our customization palette. Bug 855803 implemented the new history widget, and thus we shouldn't have multiple history widgets within our customization palette. Having multiple will just lead to user confusion and make guiding users through our support harder. The History item that will be removed is the one that toggles the visibility of the History sidebar. We will keep the History item that allows the user to view their bookmarks in a panel/popup as well as convenient access to bookmarking the current page. This bug is not concerned with removing the history sidebar.
Assignee | ||
Updated•11 years ago
|
Blocks: australis-cust
Comment 1•11 years ago
|
||
I think this is not good for toolbar customization. Of course multiple history widgets in customization palette are not elegant. However, I doubt that we need to unify it to 1 widget. If user selects the history toolbar widget from palette, he wouldn't use the other one. So there is no multiple history widgets on his toolbar. I feel it's no problem for user, and we would not pay the many cost for its maintenance.
Reporter | ||
Comment 2•11 years ago
|
||
The other approach we can take here is to rename the History sidebar widget to "History Sidebar" or "History Sidebar Toggle". Having two widgets with the name of "History" will be confusing, but we could also just change the names of them to disambiguate.
Comment 3•11 years ago
|
||
(In reply to Jared Wein [:jaws] from comment #2) > The other approach we can take here is to rename the History sidebar widget > to "History Sidebar" or "History Sidebar Toggle". Having two widgets with > the name of "History" will be confusing, but we could also just change the > names of them to disambiguate. Changing the label sounds good. I think it's easy & effective idea.
(In reply to Jared Wein [:jaws] from comment #2) > The other approach we can take here is to rename the History sidebar widget > to "History Sidebar" or "History Sidebar Toggle". Having two widgets with > the name of "History" will be confusing, but we could also just change the > names of them to disambiguate. Having a widget just to toggle a sidebar seems a bit superfluous, but "History sidebar toggle" could become a History subview entry.
Comment 5•11 years ago
|
||
as a note apart, we originally added a toggle to the bookmarks button to show/hide the sidebar, UX asked to remove it, since it's a not so common operations, and sidebars are likely going to disappear in future browsers.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → mconley
Assignee | ||
Updated•11 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 6•11 years ago
|
||
Assignee | ||
Comment 7•11 years ago
|
||
Comment on attachment 755594 [details] [diff] [review] Patch v1 This seems to do the job. Am I missing anything?
Attachment #755594 -
Flags: review?(jaws)
Attachment #755594 -
Flags: feedback?(dao)
Reporter | ||
Updated•11 years ago
|
Attachment #755594 -
Flags: review?(jaws) → review+
Assignee | ||
Comment 8•11 years ago
|
||
Comment on attachment 755594 [details] [diff] [review] Patch v1 Thanks Jared!
Attachment #755594 -
Flags: feedback?(dao)
Assignee | ||
Comment 9•11 years ago
|
||
Landed on UX as https://hg.mozilla.org/projects/ux/rev/24e7badfde21
Whiteboard: [Australis:M6] → [Australis:M6][fixed-in-ux]
Comment 10•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/24e7badfde21
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [Australis:M6][fixed-in-ux] → [Australis:M6]
Target Milestone: --- → Firefox 28
You need to log in
before you can comment on or make changes to this bug.
Description
•