W3C home > Mailing lists > Public > public-pointer-events@w3.org > April to June 2015

Re: Expected behavior when releasing a button after pointer capture

From: Scott González <scott.gonzalez@gmail.com>
Date: Mon, 27 Apr 2015 15:06:14 -0400
Message-ID: <CAO8i3ifJfSTbow44u+47c=+LB=U4bJC0fQ4YRLnQeCsA-12MMQ@mail.gmail.com>
To: Rick Byers <rbyers@chromium.org>
Cc: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
On Mon, Apr 27, 2015 at 1:47 PM, Rick Byers <rbyers@chromium.org> wrote:

> 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.
>

You get the pointerout/pointerleave events as you cross the boundary since
those are still fired on the capturing element. There's just no
accompanying pointerover/pointerenter events, even after releasing the
button. This is the behavior that I think should change. Once capture is
lost, if the pointer is over another element, I think there should be
events to indicate that.

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).
>

That sounds good. I've been waiting a few years for browsers to be
consistent on this.
Received on Monday, 27 April 2015 19:06:41 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 16 May 2015 00:31:59 UTC