Closed Bug 1129558 Opened 9 years ago Closed 6 years ago

Define a UX specification for dealing with multiple concurrent touches in a non-zoomable area

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: njpark, Unassigned)

References

Details

I just noticed that on Flame device, following action sequence does not register as touch event.

- Touch a button on screen with one finger
- While holding the button, touch another button with another finger
- release finger in any order.

On IPhone or Android, in most cases except where muititap is allowed by the software, it takes the first touch input as valid.  
Should we consider this scenario, or is our touch algorithm good as is?
What do you mean by "it takes the first touch input as valid"? Do either of the buttons activate?
Yes the button that was touched first gets activated.  I don't have the iphone, but mchang confirmed that it works so in ios.
Hm, interesting. The behaviour I see on android doesn't quite match but it does interpret some of those touches as taps. However I would like the FxOS team to weigh in on this and decide what the behaviour should be.
Component: Widget: Gonk → General
Product: Core → Firefox OS
See Also: → 1009684
Summary: Flame: what to do with mutitouch events with time difference between each touch? → Define a UX specification for dealing with multiple concurrent touches in a non-zoomable area
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.