Closed
Bug 819041
Opened 12 years ago
Closed 6 years ago
Set appropriate swipe sensitivity (minimum velocity and distance thresholds)
Categories
(Core Graveyard :: Widget: WinRT, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: TimAbraldes, Unassigned)
References
Details
(Whiteboard: feature=work)
It is currently too easy to accidentally invoke a swipe gesture (see bug 816353). We should figure out what appropriate values would be for the minimum velocity and distance traveled by the user's finger before we consider a gesture to be a swipe.
Reporter | ||
Updated•12 years ago
|
Whiteboard: [metro-it2]
Comment 1•12 years ago
|
||
Hi Asa, should this block a work item, story or moved to triage (V1 or V2)?
Flags: needinfo?(asa)
Comment 2•12 years ago
|
||
This blocks our page scrolling story. It's too easy, when page scrolling, to accidentally swipe-trigger the app bars.
Blocks: 831984
Flags: needinfo?(asa)
Updated•12 years ago
|
Blocks: metrov1triage
Whiteboard: [metro-it2]
Updated•12 years ago
|
Whiteboard: feature=work
Updated•12 years ago
|
No longer blocks: metrov1triage
Updated•12 years ago
|
Priority: -- → P3
Comment 3•12 years ago
|
||
FWIW, this bug seems at least somewhat related to bug 678392. The related UX idea, separate from that bug's discussion of animation, is that thresholds are important to avoid problems with accidental invocation of swipe gestures. While this bug is Metro-specific, it seems that the problem described here is associated with swipe gestures on any platform.
Updated•11 years ago
|
Priority: P3 → --
Updated•11 years ago
|
Component: Input → Widget: WinRT
Product: Firefox for Metro → Core
Assignee | ||
Updated•10 years ago
|
OS: Windows 8 Metro → Windows 8.1
Comment 4•6 years ago
|
||
This component is no longer valid. Closing bug as INVALID.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•