Closed Bug 972313 Opened 9 years ago Closed 5 years ago

When a pointing device that does not support hover is moved into the hit test boundaries of an element or one of its descendants as a result of a pointerdown event, the pointerenter event must be dispatched.


(Firefox for Metro Graveyard :: Input, defect)

Not set


(Not tracked)



(Reporter: alessarik, Unassigned)



(Whiteboard: [pointer-events] p=0)


(1 file)

User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release)
Build ID: 20131205075310

Steps to reproduce: have a test 8.1.1 which have to be passed on MetroFireFox.

Actual results:

If we will use trunc of MetroFireFox we will get PointerDownEvent and after that PointerEnterEvent

Expected results:

According to the specification we should get PointerEnterEvent and after that PointerDownEvent
Whiteboard: [pointer-events]
Component: General → Input
Test represents two handlers, which should call in correct consequence, when we use touch at screen.

Current status of testing MetroFireFox show that if we run test we get one FAIL with description "pointerenter event should have been received before pointerdown". After applying this patch we can get expected result with right consequence of events.

I am confusing with some results, when we use touch we gets PointerEnter-PointerDown-PointerDown events. Maybe it is not correct when we get DOWN events twice.
Whiteboard: [pointer-events] → [pointer-events] [triage] p=0
Attachment #8375434 - Attachment is patch: true
Attachment #8375434 - Attachment mime type: text/x-patch → text/plain
Comment on attachment 8375434 [details] [diff] [review]

AutoDeleteObject part is ok, it was mentioned in 956644.
But we agreed to not go with bug 956644 patches and go with generic version bug 970964.

Could you check and fix if needed latest m-c without bug 956644 patch queue, and only with patch from bug 970964?
Blocks: metrobacklog
No longer blocks: metrov1backlog
Whiteboard: [pointer-events] [triage] p=0 → [pointer-events] p=0
Mass close of bugs in obsolete product
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.