New issue
Advanced search Search tips

Issue 612466 link

Starred by 3 users
Status: Fixed
Owner:
nzolghadr@chromium.org
Closed: Sep 2016
Cc:
nzolghadr@chromium.org
rbyers@chromium.org
mustaq@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Captured pointer shouldn't fire boundary events

Project Member Reported by mustaq@chromium.org, May 17 2016 
In May 11 PEWG meeting, we decided to implement boundary event firing differently from current spec. The spec suggests that while a pointer is captured, boundary events (pointerenter/leave/over/out) are fired when the pointer leaves the boundary of captured element. This model needs hittesting while the pointer is captured but w/o a super-clear motivation or use case. We decided to switch to a no-boundary-events model (during capture) and gather compat data.

PEWG meeting notes:
https://www.w3.org/2016/05/11-pointerevents-minutes.html

Spec issue:
https://github.com/w3c/pointerevents/issues/61

Comment 1 by nzolghadr@chromium.org, May 17 2016

Owner: nzolghadr@chromium.org
Status: Assigned (was: Available)
Thanks Mustaq for creating this. This needs a little bit of refactoring particularly on the mouse side as well. I'll create a mouse logic refactoring issue later to make this blocked on that. Do we want this for beta 52?

Comment 2 by mustaq@chromium.org, May 17 2016 

I think it's a good-to-have bug for M52 because ideally we would want to resolve the spec issue before its widespread use. Therefore, the sooner we get the compat data, the better. However it is not a must-have for M52, partly because we have other issues to resolve.

Comment 3 by mustaq@chromium.org, Jun 29 2016

Labels: PointerEvent

Comment 4 by mustaq@chromium.org, Sep 30 2016 

We can close this, right?

Comment 5 by nzolghadr@google.com, Sep 30 2016 

I believe so.

Comment 6 by nzolghadr@chromium.org, Sep 30 2016

Status: Fixed (was: Assigned)
►

Sign in to add a comment