Re: [whatwg/dom] Proposal to improve the DOM creation api (#150)

I think this issue is getting a bit out of hand and scope. It started off as just wanting to create a simpler interface to DOM creation. We added XSS prevention as a bonus to developers to prevent many serious problems in the web. But now it's been suggested to handle adding event listeners, having binding support and delayed rendering, and keeping attribute order.

I feel, as Alex Russell did in his [Polymer Summit talk today](https://youtu.be/y-8Lmg5Gobw?t=17m15s), that we are trying to solve all problems with a single tool. As such, I wonder if we should be trying to solve each of these problems as their own APIs instead of solving everything with a single API. 

For example, @justinfagnani suggestion for a binding aware template string could be built on top of a simpler interface to DOM creation, so long as the interface allowed for that to happen. That way we can build up multiple small things that all support one another, just like the Chrome team did to create 20+ different suggestions to different APIs to support Web Components.

![image](https://user-images.githubusercontent.com/2433219/29627023-e5983d0e-87ed-11e7-850f-2f7fd6c71196.png)


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/150#issuecomment-324390296