Closed
Bug 1122291
Opened 10 years ago
Closed 4 years ago
wanted: unified location for ACTION buttons
Categories
(Firefox :: Toolbars and Customization, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: u123541, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150115030228
Steps to reproduce:
See also bug 1119821 (where I tried to start this issue).
First, I want to be clear about which action buttons I'm NOT referring to:
- Window actions: close, minimize, maximize, restore, pin, menu
The "action" buttons are: Tab/webpage{Back, forward, reload/refresh, go, stop, close}
While navigating and without actually thinking about it, when a user wishes to perform a page control action, it makes sense to just move the mouse towards the general direction of the action buttons. BUT... the current implementation forces the user to go "whoa... oh yeah, back/forward are upper-left, and the others are somewhere upper-center-right.
Whenever the user wishes to perform one of the above actions on a page, [s]he must first take time to decide in which direction to head.
This request is to either a) allow users to be in full control over these buttons' locations, or b) corral them into one location, so that the button selection can be eye-selected while still moving the mouse to the corral, rather than having to first decide which pasture (east or west) to move towards.
Note that I've added "tab close" to the list. MANY times, I first have to scroll the tabs until I find the currently active one if I want to close it. With a single "close active tab" button in the above mentioned "corral", I would object to the removal of all the individual tab close buttons -- not to mention accidentally hitting them on occasion and having to go thru History->Recently closed....
Updated•10 years ago
|
Component: Untriaged → Toolbars and Customization
Comment hidden (advocacy) |
Updated•4 years ago
|
Resolution: WONTFIX → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•