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

This definitely feels like the darts are getting closer to the bullseye.  With all the bright people looking at this there has to be a solution that satisfies what everyone loves about `is` yet no one can say that it's confusing, not DRY, violates the Liskov Substituion principle, is vague with respect to element type identification (@trusktr comments), etc.

In other words, instead of introducing a `content` element for the shadow dom, and then later changing it to `slot`, lets just find the right solution to start with.  

-- 
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-264338664