Re: [webcomponents] On-demand custom elements using modules (#444)

Yeah, thinking on it, I guess it's not a particularly great idea to do it this way.  You could replace those property sets with attribute sets but it might cause confusion.  I was stuck in the mindset of how our current approach works; we define and re-set the properties in `createdCallback` as we _currently_ have a requirement to support IE 8.  In a proper setup, pre-existing properties would sit on the element in front of those defined on the prototype, which would be problematic.

In our next release we're dropping support for everything before IE 11, so it's a good time to re-evaluate our approach and do things properly.  Recommending `import` and `System.import`, along with the MO method, is probably the right thing to do.

---
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/444#issuecomment-197783867