Re: [w3ctag/design-reviews] Pointerevent extension (#346)

We discussed this in our telecon today and we're happy with the use case and the broad design here.

Happy to close this, but just some parting thoughts:

- We have some mild concern that the naming around `getCoalescedEvents` uses a word which is uncommon and difficult to spell, and is likely to be difficult for folks whose English vocabulary is not advanced for whatever reason. Something like `getBundledEvents` might be easier for more people to understand.

- The spec text seems a bit rough, with a lot of long, hard to read paragraphs and some ReSpec warnings, and the editors would presumably want to clean it up at some point. We mention this because it made the review more difficult, and presumably implementers would also find it difficult to digest.

Thank you for your patience through this review process, and for your hard work on this API.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/346#issuecomment-505730501