User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0 Referencing https://bugzilla.mozilla.org/show_bug.cgi?id=582485 The history drop down button is one of the most used features by end users. The button itself is a quicker alternative than the click and hold, or right click options that are currently in use. Even though commenter on with 582485 believe this was a heavily button it was removed without any reasons for doing so from any technical perspective. Indeed the only logic was to copy the look and feel of other browsers, for ME TOO aesthetics. As the removal was done via bugsheet, this request should be equally served as was 582485 The removal of the drop down history button has these effects. Lost User Interface functionality and ergonomics: One of the largest population of users are laptops with a touch pad. With the button, users can use ONE finger, and a double bounce on the touchpad to select and click. Click and hold with only a touchpad (no button) while technically possible is hugely impractical to end users. Thus to use the drop down feature a second finger or second key must be done. Thus the UI ergonomics are significantly decreased. Click and hold, or a 2nd button click, are significantly slower than a button, and a significant requirement to users with disabilities. It requires more dexterity and also moving of the mousing to a second trigger. There is ZERO downside to having the button functionality whether within the forward and back set, or a separate button, within turn key look and feel, or if only provided as an optional button. Reproducible: Always Steps to Reproduce: 1. Open Firefox 2. Drop down functionality available---can not be accessed via any dedicated button button. NOTE: Click and hold/right click is not a replacement...its only an alternative, with different attributes as an end user solution. Actual Results: 582485 removes the UI functionality, and changes overall look and feel to end users. Expected Results: Functionality as within Firefox 3. Or within TOOLS, OPTIONS, the ability to include the button. Without incorporation into the standard releases of Firefox, THEME designers will not have a standard reference. This was the third button from the left, it was used significantly, no thought was given to end user experience or benefits or impacts to the change of the GUI. Removal via bug warrants replacement via same. One 3 add-on fixes have quickly been created, the lack of standardization of an add-on solution, is significant overhead for the community. Such a common button as featured in Firefox 3, should remain part of the ongoing build.

Unsupported add-ons, which attempt to replace functionality. Again functionality is key for laptop users and users with disabilities. https://addons.mozilla.org/en-us/firefox/addon/backforedrop/ https://addons.mozilla.org/en-us/firefox/addon/backforward-dropmarker/

(In reply to comment #0) > Click and hold, or a 2nd button click, are significantly slower than a button, > and a significant requirement to users with disabilities. It requires more > dexterity and also moving of the mousing to a second trigger. I don't see how right click is any harder than left click. Btw, all of this has been brought up many times and already answered and evaluated. A decision has been made taking in count all the feedback. Add-ons or third party themes can fix it, if there is a large enough request there won't be any problem from this point of view.

(In reply to comment #2) > (In reply to comment #0) > > Click and hold, or a 2nd button click, are significantly slower than a button, > > and a significant requirement to users with disabilities. It requires more > > dexterity and also moving of the mousing to a second trigger. > > I don't see how right click is any harder than left click. > Btw, all of this has been brought up many times and already answered and > evaluated. A decision has been made taking in count all the feedback. > Add-ons or third party themes can fix it, if there is a large enough request > there won't be any problem from this point of view. > > *** This bug has been marked as a duplicate of bug 606888 *** 1. This is raised as an "access" issue as highlighted by keyword, the issues raised within, are not duplicated in 60688. 2. Any extensive discussion on this decision is not referenced, and it pure fallacy to believe that since a decision has been made that it must have taken into consideration all things. All accounts of process that this removal of functionality, shows the decision was made haphazardly, as is reflected in 582485. 3. Add-ons, and the requirements to integrate them for themes and other supported functionality, it not a workaround for the removal of long established and heavily used functionality. 4. People with disabilities (such as cerebral palsy) have a harder time dealing with switching fingers, switching buttons, holding buttons down for extended periods. This is why its an access issue. 5. Clicking and holding is slower, you have to wait for the popup. Using a second finger is slower, and requires the right button and dexterity. There make the new method a poor replacement. 6. A very very high number of users...use trackpads, which require one finger, and clicking and double-clicking by the same single finger on this touchpad. The right click can not be done exclusively on the touchpad. When a browser makes a change on how a large segment of users must interact with major functionality, its a real issue. 7. The bug sheet that caused the change, did not fix any items, but did break items, and made items not work....what was working was "FIXED" and broken as a result. The removal of these functionality is error, and a loss to Firefox users. The removal of these functionality was improperly removed via a bug sheet, when it should now be clear that a more robust understanding of the interconnectedness and user reliance of the feature should have been done. Again for all of the above, this report is NOT a duplicate of other requests, and the consideration to disability access raised here has NOT been discussed at all.

so, provided that the arrow won't come back (bug 606888 is wontfix), what are your suggestions in this bug to solve the problem? If no suggestions, this is still a dupe since it's just asking to bring back the arrow, that won't happen.

Also, you should have brought your thought on mozilla.dev.usability, where user experience team could have discussed and answered them, rather than in a bug.

Why do you insist that the arrow button will not come back? There seems to be no logic for its removal, no consideration, and what seems to be a circle the wagons for past decisions for no logical reason. Beyond the bug sheet cited, where is this discussed elsewhere? As the functionality was removed via bug, why should it not be restored via same?