Closed Bug 819041 Opened 12 years ago Closed 5 years ago

Set appropriate swipe sensitivity (minimum velocity and distance thresholds)

Categories

(Core Graveyard :: Widget: WinRT, defect)

Product:
Core Graveyard
Component:
Widget: WinRT
Platform:
All
Windows 8.1
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
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.
Depends on: 819042
Whiteboard: [metro-it2]
Hi Asa, should this block a work item, story or moved to triage (V1 or V2)?
Flags: needinfo?(asa)
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)
Blocks: metrov1triage
Whiteboard: [metro-it2]
Whiteboard: feature=work
No longer blocks: metrov1triage
Priority: -- → P3
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.
No longer blocks: 831984
Priority: P3 → --
Component: Input → Widget: WinRT
Product: Firefox for Metro → Core
OS: Windows 8 Metro → Windows 8.1
This component is no longer valid. Closing bug as INVALID.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.