Pulling down Back/Forward menu requires an unnecessary delay

VERIFIED FIXED in Firefox 6

Status

()

Firefox
Toolbars and Customization
VERIFIED FIXED
6 years ago
6 years ago

People

(Reporter: David Regev, Assigned: dao)

Tracking

({ux-efficiency})

unspecified
Firefox 6
ux-efficiency
Points:
---
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [parity-Chrome][parity-IE])

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

6 years ago
User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0

(Continued from bug 582485 comment #38)

If you want to bring up the Back/Forward menu (without right-clicking), you must click and hold. The hold is required in order to differentiate between going Back/Forward immediately and bringing up the menu. Thus, if you want to go back to a specific page, you must click, hold until the menu pops up, drag down/up to the desired history item, and release. The problem is that the hold is unnecessary if you’re going to be pulling down/up this menu. If you click on the Back button and then drag it down, there is no ambiguity: you can only possibly want to see the history menu.

Thus, the proposed solution is to remove the need for holding when pulling up/down the Back/Forward menu and show it the menu immediately.

Fixing this bug will also remove the regression introduced by removing the Back/Forward dropdown (bug 582485): it’s no longer possible to bring up the Back/Forward menu quickly.

Reproducible: Always

Steps to Reproduce:
1. Click down on Back button.
2. Don’t wait!
2. Drag down.
Actual Results:  
Nothing.

Expected Results:  
Back/Forward menu appears.

The proposed solution is already implemented by Google Chrome.
(Reporter)

Updated

6 years ago
Blocks: 582485
Keywords: ux-efficiency
Whiteboard: [parity-Chrome]
(Assignee)

Updated

6 years ago
Status: UNCONFIRMED → NEW
Component: General → Toolbars
Ever confirmed: true
QA Contact: general → toolbars

Comment 1

6 years ago
I believe this is not a complete solution to the problems introduced by 582485.  The removal of the button, and a buttons functionality are not replaced the unique methods of accessing the functions.

1.  582485 requires waiting, holding, and or using additional buttons.

2.  Original FF 3.6 and all previous FF has the button.  
  a.  You click button.  Menu appears.
  b.  You hover (select) the previous URL, and you click again.   You are done.  Its a Click, select, Click.   (can be done on trackpad with no buttons)

New options are.  
Click, Hold, wait, release, highlight,click again  (Requires trackpad and buttons, holding pressure on buttons)

or 

Right Click, select LEFT click.   (requires two buttons and trackpad)

----The simple solution is the return of the old button, the new functionality as current in 4.0, does not need to be removed.   

Advocates 582485 did not do proper due diligence to the impact of the removal.  Even with the proposals here, the quickness and the directness a button, is not replaced.

Comment 2

6 years ago
(In reply to comment #1)

> ----The simple solution is the return of the old button, the new functionality
> as current in 4.0, does not need to be removed.   
> 
> Advocates 582485 did not do proper due diligence to the impact of the removal. 
> Even with the proposals here, the quickness and the directness a button, is not
> replaced.

I agree.
(Reporter)

Comment 3

6 years ago
(In reply to comment #1)
> I believe this is not a complete solution to the problems introduced by 582485.

This solution is just as efficient as the previous method, if not more so. Previously, what many people were used to doing is: click on dropdown, find desired page, and click again. Now, they're forced to be quicker about it: click down on on of the buttons (any one will do), drag down to the desired page, and let go. It’s all one click, one quick gesture. Moreover, removing the dropdown removes the choice between going to one of the buttons and going to the dropdown. This reduces time (and mental overhead) due to Hick’s Law.
Whiteboard: [parity-Chrome] → [parity-Chrome][parity-IE]

Comment 4

6 years ago
> 
> This solution is just as efficient as the previous method, 

David, I read again you solution, and I think I understand it better.   You are saying when I click back, it tosses up the history dropdown, and then when I move my mouse off that button it fades out.....or I click on one of them.

This would be an improvement over the current method of in FF 4, and it would instantly solve the need to understand how it is to work...it shows right up.

Some may find it a bit messy or busy, but it would be functional.  It also supports my criteria for ACCESS consideration of some users.   That it can be done with one button, and or, with a trackpad and zero buttons.

Developers need to realize that point and click, is much less of a burden than click and hold, or right mouse click, for some users than others.

So I support the idea of this solution....but do not retract what I believe is a real need to give users the button back again.   

We agree and see the same problem, we are both trying to fix what functionality that was removed, by misstating it as a software defect, instead of the designed functionality it was.
(Reporter)

Comment 5

6 years ago
(In reply to comment #4)
> David, I read again you solution, and I think I understand it better. You are
> saying when I click back, it tosses up the history dropdown, and then when I
> move my mouse off that button it fades out.....or I click on one of them.

Not exactly. When you click on Back (or Forward) and “drag” the button down, the menu appears. It’s the same as pulling down what is known as a pull-down menu, such as the File menu. If you want to see how this works in practice, try doing this in Chrome or Internet Explorer 9.
(Assignee)

Comment 6

6 years ago
Created attachment 533932 [details] [diff] [review]
patch
Assignee: nobody → dao
Status: NEW → ASSIGNED
Attachment #533932 - Flags: review?(gavin.sharp)
(Assignee)

Updated

6 years ago
Attachment #533932 - Flags: review?(gavin.sharp) → review?(sdwilsh)
I take it we don't have a test for this, right?
(Assignee)

Comment 8

6 years ago
Not that I know of. There's http://hg.mozilla.org/qa/mozmill-tests/file/c211c062c5b5/tests/functional/testToolbar/testBackForwardButtons.js for clicks.
(In reply to comment #8)
> Not that I know of. There's
> http://hg.mozilla.org/qa/mozmill-tests/file/c211c062c5b5/tests/functional/testToolbar/testBackForwardButtons.js
> for clicks.
Would it be a lot of work to add one with this bug?
(Assignee)

Comment 10

6 years ago
Created attachment 534581 [details] [diff] [review]
patch

added a test
Attachment #533932 - Attachment is obsolete: true
Attachment #533932 - Flags: review?(sdwilsh)
Attachment #534581 - Flags: review?(sdwilsh)
(In reply to comment #10)
> added a test
Thanks a ton :)  I should get to this review in a couple of hours.
Comment on attachment 534581 [details] [diff] [review]
patch

Review of attachment 534581 [details] [diff] [review]:
-----------------------------------------------------------------

Could you please add the pd license block (https://www.mozilla.org/MPL/boilerplate-1.1/pd-c) to the test file?

r=sdwilsh
Attachment #534581 - Flags: review?(sdwilsh) → review+
(Assignee)

Comment 13

6 years ago
http://hg.mozilla.org/mozilla-central/rev/381e9216f883
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → Firefox 6

Comment 14

6 years ago
This fix is great for people who know about it, but is it discoverable enough?
(Assignee)

Comment 15

6 years ago
(In reply to comment #14)
> This fix is great for people who know about it, but is it discoverable
> enough?

Bug 619930 wants to add a hint to the tooltip. If you have alternative ideas, please file new bugs.
Mozilla/5.0 (Windows NT 5.1; rv:6.0a2) Gecko/20110525 Firefox/6.0a2

Verified issue using the STR from Comment 0 on Win XP, Win 7, Ubuntu, Mac OS X 10.6.
Status: RESOLVED → VERIFIED
I'm finding that very fast click and pull down gestures aren't registering.  Is there any timer or threshold here?
(Assignee)

Comment 18

6 years ago
There's no timer; it could have to do with the button being round on Windows and OS X.
You need to log in before you can comment on or make changes to this bug.