Re: [w3c/webcomponents] defining and instantiating customized built‐in elements as if they were autonomous custom elements (#613)

Just want to point out a few more things that are indirectly relevant.  In the [V1 shadom dom](https://developers.google.com/web/fundamentals/getting-started/primers/shadowdom) spec we have a NOTICE section pointing out:

> Why you should never create web components with {mode: 'closed'}:

So why is it in the spec?  Why are we all reading about something that we should never really use and that is useless?  If we can come up with better solutions, then why did we not just do that in the first place?

Also this [HTML Imports](https://www.html5rocks.com/en/tutorials/webcomponents/imports/) document refers to using the `<script type="text/html">)` element as a **CrazyHack**.  So if we invented HTMLImport to get around the **CrazyHacks** approach then should not custom elements be THE TOOL for avoiding crazy hacks in the future and maintaining usage symmetry across html web development activities?

-- 
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/613#issuecomment-264611031