New issue
Advanced search Search tips

Issue 633679 link

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



Sign in to add a comment

Relative ordering of boundary events and got/lostpointercapture events

Project Member Reported by mustaq@chromium.org, Aug 2 2016 
Ideally we would the capturing node to receive all pointerevents including the boundary events. This is possible when gotpointercapture is dispatched after the boundary events for the pointer, and lostpointercapture is dispatched before the boundary events for the pointer.

https://github.com/w3c/pointerevents/issues/39#issuecomment-193966884

IIRC our implementation used to be ideal but this is no longer the case. We will fix it if easy.
Project Member

Comment 1 by bugdroid1@chromium.org, Dec 19 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/eff55a14abadd957d1ebf8cfd897ce6c6892b3c3

commit eff55a14abadd957d1ebf8cfd897ce6c6892b3c3
Author: nzolghadr <nzolghadr@chromium.org>
Date: Mon Dec 19 23:23:28 2016

Send boundary events before gotpointercapture

This CL sends boundary events before gotpointercapture
as if gotpointercapture can trigger boundary events
like a move event. This kind of makes sure that
there will be no boundary events between got and lost
pointer capture events which might be more intuitive.

At this time Edge behavior differs from both the behavior in
this CL and before this cL as they were sending boundary
events regardless of the capture and using the hit-tested
target. However, they are planning to catch up here.

BUG= 633679 

Review-Url: https://codereview.chromium.org/2521993003
Cr-Commit-Position: refs/heads/master@{#439609}

[modify] https://crrev.com/eff55a14abadd957d1ebf8cfd897ce6c6892b3c3/third_party/WebKit/LayoutTests/fast/events/pointerevents/mouse-pointer-capture-expected.txt
[modify] https://crrev.com/eff55a14abadd957d1ebf8cfd897ce6c6892b3c3/third_party/WebKit/LayoutTests/fast/events/pointerevents/mouse-pointer-capture-transition-events-expected.txt
[modify] https://crrev.com/eff55a14abadd957d1ebf8cfd897ce6c6892b3c3/third_party/WebKit/LayoutTests/fast/events/pointerevents/mouse-pointer-capture.html
[modify] https://crrev.com/eff55a14abadd957d1ebf8cfd897ce6c6892b3c3/third_party/WebKit/LayoutTests/fast/events/pointerevents/touch-capture-expected.txt
[modify] https://crrev.com/eff55a14abadd957d1ebf8cfd897ce6c6892b3c3/third_party/WebKit/Source/core/input/EventHandler.cpp
[modify] https://crrev.com/eff55a14abadd957d1ebf8cfd897ce6c6892b3c3/third_party/WebKit/Source/core/input/PointerEventManager.cpp
[modify] https://crrev.com/eff55a14abadd957d1ebf8cfd897ce6c6892b3c3/third_party/WebKit/Source/core/input/PointerEventManager.h

Comment 2 by nzolghadr@chromium.org, Dec 20 2016

Status: Fixed (was: Assigned)
►

Sign in to add a comment