W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2014

Re: Compatibility events

From: Arthur Barstow <art.barstow@nokia.com>
Date: Wed, 22 Jan 2014 09:03:29 -0500
Message-ID: <52DFCFB1.4040604@nokia.com>
To: Sangwhan Moon <sangwhan@iki.fi>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>
Hi Sangwhan, All,

It appears no one ever replied to this thread [1] and although it was a 
proposed topic on some draft meeting agendas, Sangwhan was not present 
during those meetings so the topic was dropped.

What - if anything - do we want to do here with the Pointer Events spec?

-Thanks, ArtB

[1] 
<http://lists.w3.org/Archives/Public/public-pointer-events/2013OctDec/0018.html>

On 10/22/13 2:29 AM, ext Sangwhan Moon wrote:
> (Unleashing the elephant in the room to stomp and dance)
>
> The current spec is written under the circumstances that implementations
> do not have support for touch events nor compatibility pointer events from
>
>
> non-pointer devices.
>
> Continuing the recent discussion on relations between pointer/touch/mouse
> events and when and how to fire them - I've been wondering if some authors
> could make use of a method that could be called upon page initialization
> to tell the implementation to fire only pointer events, and nothing else.
>
> As per current spec, this is possible when the pointer is primary and
> pointerdown is canceled. No details on what to do with TE, which generates
> both touch events and mouse events.
>
> Additionally, there are keyboard/joystick only navigation devices which use
> anchoring on focusable elements (Opera calls this "spatial navigation") which
> have so far generated mouse events as navigating to just the href never actually
> worked in practice - I believe implementations that have this feature will need to
> generate pointer events in the future since the long term goal is probably to use
> more PE in practice.
>
> While there is a CG being discussed, it would be nice to know how much we
> can cover in the spec without adding overhead. (Spatial navigation is probably
> fine, but that's a bit of a minor feature)
>
Received on Wednesday, 22 January 2014 14:04:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:26 UTC