Closed
Bug 816353
Opened 12 years ago
Closed 12 years ago
Scroll-to-top and scroll-to-bottom gestures are easy to trigger accidentally while fling-scrolling
Categories
(Firefox for Metro Graveyard :: Input, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mbrubeck, Assigned: mbrubeck)
Details
(Keywords: ux-error-prevention, Whiteboard: [metro-mvp][LOE:1][metro-it2][completed-elm])
Attachments
(1 file)
(deleted),
patch
|
TimAbraldes
:
review+
|
Details | Diff | Splinter Review |
I frequently trigger swipe gesture commands (e.g. swipe to scroll to top or bottom of the page) by accident while I'm just trying to scroll quickly.
Can we switch to multi-finger swipes for these commands? This would reduce the conflict with "fling" scrolling, and would be consistent with our support for trackpad gestures.
If we do change this, we'll need to change how these gesture events are detected and dispatched in our widget code. (Maybe the event should have a property that counts the number of fingers on the screen.)
Comment 1•12 years ago
|
||
I would love to ditch single-finger swipes for exactly the reason you mention. Windows doesn't provide support for multi-finger swiping [1][2] but I think we could accomplish this by keeping a count of the number of different pointerIDs we see during a gesture. Then when the gesture is complete and we determine that it is a swipe, we can verify that it had the correct number of fingers.
[1] http://social.msdn.microsoft.com/Forums/en-US/winappswithcsharp/thread/b9680637-4da5-4c69-9015-c32bb2d1686b
[2] http://social.msdn.microsoft.com/Forums/en-US/toolsforwinapps/thread/7fddff93-71f6-4871-85b5-2c8bd69344e2
Comment 2•12 years ago
|
||
This is an annoying bug, we need to test whether or not this can be tweaked through widget. We may also have other solutions to similar problems.
Whiteboard: [metro-mvp?] → [metro-mvp][LOE:1]
Assignee | ||
Comment 3•12 years ago
|
||
We might just want to remove the scroll-to-top and scroll-to-bottom gestures; they are not very discoverable anyway. Other mobile browsers like Opera have nice discoverable UX for scrolling long distances.
Summary: Require multi-finger swipes for navigation, to avoid conflict with panning → Scroll-to-top and scroll-to-bottom gestures are easy to trigger accidentally while fling-scrolling
Assignee | ||
Comment 4•12 years ago
|
||
Yuan agreed on IRC that we should just remove the swipe up/down gestures. They are unintentional leftovers from XUL Fennec (where they did require multiple fingers).
Assignee: nobody → mbrubeck
Keywords: uiwanted
Hardware: x86_64 → All
Whiteboard: [metro-mvp][LOE:1] → [metro-mvp][LOE:1][metro-it2]
Assignee | ||
Comment 5•12 years ago
|
||
This removes the vertical swipe gestures for now; we should file a separate bug to find a better way to support scrolling long distances.
Attachment #689440 -
Flags: review?(tabraldes)
Assignee | ||
Updated•12 years ago
|
Status: NEW → ASSIGNED
Comment 6•12 years ago
|
||
Comment on attachment 689440 [details] [diff] [review]
patch
Review of attachment 689440 [details] [diff] [review]:
-----------------------------------------------------------------
This seems fine as long as scrollContentToTop and scrollContentToBottom don't have any other consumers (keyboard shortcuts maybe?)
Attachment #689440 -
Flags: review?(tabraldes) → review+
Assignee | ||
Comment 7•12 years ago
|
||
https://hg.mozilla.org/projects/elm/rev/aa9418a727e8
(In reply to Tim Abraldes (:tabraldes) from comment #6)
> This seems fine as long as scrollContentToTop and scrollContentToBottom
> don't have any other consumers (keyboard shortcuts maybe?)
Nope, no other callers.
Whiteboard: [metro-mvp][LOE:1][metro-it2] → [metro-mvp][LOE:1][metro-it2][completed-elm]
Assignee | ||
Comment 8•12 years ago
|
||
Resolving bugs in the Firefox for Metro product that are fixed on the elm branch. Sorry for the bugspam. Search your email for "bugspam-elm" if you want to find and delete all of these messages at once.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
OS: Windows 8 Metro → Windows 8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•