Re: Expected behavior when releasing a button after pointer capture

Good question.  If possible I would like the spec to cover these sort of
cases - we've had no end of problems with differences between browsers in
this sort of regard for mouse events.   Perhaps now is our chance to
prevent such issues in the future for PE?

FWIW, I'd say it's a bug not to send pointerleave to an element the mouse
is no longer on after release of capture (including by button up).  It
would be wrong for a framework to consider such elements still hovered.

The question of what should happen when content appears underneath is very
similar to the question of what should happen when the content scrolls.  WebKit
has just changed their behavior here
<https://bugs.webkit.org/show_bug.cgi?id=99940>, and we're planning on
changing blink <https://code.google.com/p/chromium/issues/detail?id=317007>
- probably to something similar to Firefox
<https://code.google.com/p/chromium/issues/detail?id=317007#c26> (or
possibly WebKit).

Rick


On Mon, Apr 27, 2015 at 12:23 PM, Scott González <scott.gonzalez@gmail.com>
wrote:

> If an element has pointer capture enabled and you move out of the element
> into another element, then release the button, what is the expected series
> of events after releasing the button?
>
> In IE11, you only get a pointerup event on the capturing element. The
> pointer must then be moved again in order to get pointermove, poinerover,
> and pointerenter on the element that's currently hovered.
>
> The closest scenario I can think of with mouse events is having an element
> appear directly under the mouse. I believe Firefox is still the only
> browser that fires events when the element becomes visible. See
> http://dev-test.nemikor.com/behavior/mouseover-when-element-is-shown.html
>
> Should we document this behavior to ensure it's consistent across
> browsers? What's the current behavior in the Firefox implementation?
>