- From: Domenic Denicola <notifications@github.com>
- Date: Fri, 12 Aug 2016 19:35:43 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Saturday, 13 August 2016 02:36:10 UTC
I think the correct approach for this, and other ways of matching native element conventions (like attribute reflection, or enumerated attributes, or token list attributes, or URL attributes, ...) is to see what developers in library space. E.g., if we see popular frameworks or libraries doing this, it makes sense to possibly bake such a helper in to the platform. But I don't think we should do so before we've given the ecosystem a chance to explore the problem space independently of standardization efforts. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/546#issuecomment-239597256
Received on Saturday, 13 August 2016 02:36:10 UTC