1194963 - No pointer event is dispatched when a physical contact with digitizer is made - Windows 8 touch screen

Status: RESOLVED WORKSFORME

(Firefox :: Untriaged, defect)

Description

[damianstefaniak1987]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36

Steps to reproduce:

I found an issue with pointer events relating to Windows 8 touch screen devices using  FF Nightly v. 41.0a2. 

When I "touchstart" the screen nothing happens. The first event is dispatched only when I remove or move the pointer (finger).



Actual results:

The sequence of events dispatched is but only after my pointer (finger moves or leaves the digitizer): 
pointerover > pointermove > mousemove > pointerdown > mousedown > pointerup > mouseup > pointerover

See quick jsfiddle made:
http://jsfiddle.net/sng8rq3j/11/


Expected results:

According to the w3c pointer events spec:

"3.2.2 The pointerdown event

A user agent must dispatch this event when a pointer enters the active buttons state. For mouse, this is when the the device transitions from no buttons depressed to at least one button depressed. For touch, this is when physical contact is made with the digitizer. "

My understanding of this spec is that I make a physical contact with the digitizer of a device 'pointerdown' event should be dispatched.

Comment 1

[damianstefaniak1987]

*Actual results:
The sequence of events dispatched is as follows (but only after my pointer [finger] moves or leaves the digitizer)...

Comment 2

[damianstefaniak1987]

Does the absence of any pointer event dispatched in the situation described above relates to lack of support of touch events for desktop devices at the moment?

I used about:config to change flags to enable touch events. However, it doesn't solve the issue as no touch event is dispatched.

Comment 3

[Kartikaya Gupta (email:[e-mail])]

(In reply to damianstefaniak1987 from comment #0)
> I found an issue with pointer events relating to Windows 8 touch screen
> devices using  FF Nightly v. 41.0a2. 

As of the last Tuesday the current Nightly builds are v43, so either you're using a really old Nightly, or (more likely) you're using a slightly-old Developer Edition build. Can you please re-test on a recent Nightly?

> My understanding of this spec is that I make a physical contact with the
> digitizer of a device 'pointerdown' event should be dispatched.

Yes, I believe that's correct.

(In reply to damianstefaniak1987 from comment #2)
> Does the absence of any pointer event dispatched in the situation described
> above relates to lack of support of touch events for desktop devices at the
> moment?

It might.

> I used about:config to change flags to enable touch events. However, it
> doesn't solve the issue as no touch event is dispatched.

Which flags did you change? I believe you need to set the "dom.w3c_touch_events.enabled" pref to 1 for this to work.

Comment 4

[damianstefaniak1987]

> I found an issue with pointer events relating to Windows 8 touch screen
> devices using  FF Nightly v. 41.0a2. 


As of the last Tuesday the current Nightly builds are v43, so either you're using a really old Nightly, or (more likely) you're using a slightly-old Developer Edition build. Can you please re-test on a recent Nightly?

- I've updated FF and tested v 42.0a2 (aurora update channel Firefox Developer Edition) and it works great both pointer events and touch events. Thanks for your quick reply.

> I used about:config to change flags to enable touch events. However, it
> doesn't solve the issue as no touch event is dispatched.


Which flags did you change? I believe you need to set the "dom.w3c_touch_events.enabled" pref to 1 for this to work.

- Yes, that was the flag I changed along with "dom.w3c_pointer_events.enabled" prev set to true.

I think we can mark the issue as solved.

Comment 5

[Kartikaya Gupta (email:[e-mail])]

Thanks for verifying!