Closed
Bug 1292041
Opened 9 years ago
Closed 8 years ago
Touching an element fires twice on pointerenter and pointerleave
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1285070
People
(Reporter: brooke, Assigned: stone)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160606114227
Firefox for Android
Steps to reproduce:
Firefox 48 on Windows 10 Mobile (a tablet)
about:config:-
dom.w3c_touch_events.enabled = 2
dom.w3c_pointer_events.enabled = true
layout.css.touch_action.enabled = true
CSS style:-
span.a-shell {
-moz-user-select: none;
touch-action: none;
display: block;
cursor: pointer;
outline: none;
}
Element to test:-
<span class='a-shell' tabindex='-1' draggable='false' onpointerup=\"up(this,event);\" onpointerdown=\"down(this,event);\" onpointerenter=\"enter.main(this,event);\" onpointerleave=\"leave.main(this,event);\">Test</span>
The following events sequence were recorded after touching down-&-up on the above element:-
1) enter
pointerType: touch
2) down
pointerType: touch
3) up
pointerType: touch
4) leave
pointerType: touch
5) enter
pointerType: mouse
6) leave
pointerType: mouse
The last 2 mouse events were unexpected. They should not happen.
Actual results:
The last 2 mouse events were unexpected. They should not happen, since it was a 'touch'.
Expected results:
Only the first 4 touch events should happen.
Summary: Touching an element ires twice on pointerenter and pointerleave → Touching an element fires twice on pointerenter and pointerleave
Updated•9 years ago
|
Flags: needinfo?(botond) → needinfo?(sshih)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → sshih
Assignee | ||
Updated•9 years ago
|
Flags: needinfo?(sshih)
Assignee | ||
Comment 2•8 years ago
|
||
Test Firefox [1] on Windows10 and it works fine
[1] https://hg.mozilla.org/mozilla-central/rev/054d4856cea6
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•