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

Feedback on pointer events

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 3 Feb 2014 17:47:36 +0000
Message-ID: <CADnb78g0UFyJhcvSGTcQxEwOW83ixUKTx9L2yDrQFz64fFptpw@mail.gmail.com>
To: public-pointer-events@w3.org
Hi,

bz and I had a brief look at this specification earlier today and
found a number of issues.

1. PointerEvent constructor is not defined. You probably just want to
reference http://dom.spec.whatwg.org/

2. The only place that maps event names (types) to their corresponding
interface is non-normative.

3. Instead of dispatch you want to talk about firing events, see
http://dom.spec.whatwg.org/#concept-event-fire for the general idea
and http://xhr.spec.whatwg.org/#concept-event-fire-progress for how to
do it on an Event subclass. You will have define how to set all the
properties of the class as well.

4. You cannot talk about "asynchronously" dispatch this day and age.
You'll have to define how your standard interacts with the event loop:
http://www.whatwg.org/specs/web-apps/current-work/#event-loop

5. Why is pointercancel cancelable?

6. A bunch of events are cancelable. In order to define that properly
you need to define something like a) Fire an event /x/; b) If /x/'s
canceled flag is unset, run Y. Otherwise it is unclear what needs to
happen.

7. Why is maxTouchPoints not exposed on Screen?

8. It would be much better if pointer capture became part of the
overall dispatching model rather than a separate set of steps you have
to merge in your head with what came before (and hope it still makes
sense!).

Cheers,


-- 
http://annevankesteren.nl/
Received on Monday, 3 February 2014 17:48:04 UTC

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