- From: <bugzilla@jessica.w3.org>
- Date: Mon, 13 Jul 2015 18:53:57 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28938 Jacob Rossi [MSFT] <jrossi@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrossi@microsoft.com --- Comment #1 from Jacob Rossi [MSFT] <jrossi@microsoft.com> --- We've discussed this scenario a few times in the Touch Events and Pointer Events groups. It seems useful to a certain set of folks. I don't have any initial concerns with your spec proposal. Most of my questions stem from the roadmap for this feature beyond just firesTouchEvents. Do you have any consumers of the polyfill that are helping validate this satisfies their needs? Given we're creating a new interface here for this rather than a single property, I'd love to know if you have a scope in mind for what other types of information might eventually get added to SourceDevice (is it input characteristic properties, such as discussed in [1], or just info about how the events/model will be processed like firesTouchEvents; should we also have a firesPointerEvents property?). Given it seems set up intentionally for more members than just the one in the spec today and given UI Events is fairly far along as a spec, I think this makes more sense as a standalone spec in the new Incubator Community Group. [1]https://lists.w3.org/Archives/Public/www-dom/2015JanMar/0121.html -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 13 July 2015 18:54:03 UTC