Closed Bug 640447 Opened 14 years ago Closed 14 years ago

Add tooltip on Back arrow informing user of how to get history dropdown

Categories

(Firefox :: Toolbars and Customization, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 619930

People

(Reporter: ametedinov, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0 Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0 The beta (4.0) version of Firefox does NOT keep the feature from Firefox 3.x which allows the user to go back to a previously visited page. I am talking about the arrow which exists in the 3.x version right next to the back button. When you press that arrow, you get a list of previously visited pages and you can go back to the page you visited 10 pages ago. This feature is ESSENTIAL because many webpages force you to stay on their page by not letting you go back simply by pressing the back button. Reproducible: Always
Right click on the back arrow and the list is there
Component: General → Toolbars
QA Contact: general → toolbars
Version: unspecified → Trunk
Works for Me on: Mozilla/5.0 (Windows NT 6.1; rv:2.0b13pre) Gecko/20110309 Firefox/4.0b13pre *Note: As in Comment 1, right clicking the back arrow gives the same results as in Firefox 3.x (small arrow)
Thanks for the info. This functionality is not very obvious however. To make it more apparent, can you change the tooltips for the back and forward buttons as follows: --Back button Current: "Go back one page" Suggested: "Go back one page; right click for more options" --Forward button Current: "Go forward one page" Suggested: "Go forward one page; right click for more option"
Severity: normal → enhancement
typo: the last word should have been "options" not 'option'
OS: Windows 7 → All
Hardware: x86 → All
Summary: Back multiple times → Add tooltip on Back arrow informing user of how to get history dropdown
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.