Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

Here's something that's indirectly related.  If we read up on the [Shadow DOM V1 Spec](https://developers.google.com/web/fundamentals/getting-started/primers/shadowdom) we see a lot of examples like this:

> header.attachShadow({mode: 'open'});

And then when we get to the bottom of the spec there's a big section creating closed shadow roots and why we should avoid this (NEVER EVER EVER EVVERRR Ever DO THIS).

> div.attachShadow({mode: 'closed'})

So you step back for a moment and say "OK if we should never make it closed, then why do all the example calls declare it to be open?.  Why is this not just the default?"  Or maybe it is, but it's hard to tell from the write up and it definitely seems like something is broken in the W3C process.

If we took this type of approach in manufacturing we would get a lot of recalls.  Recalls are expensive.  It's a lot more profitable to make sure the quality is tight upfront.  It also leads to happy customers.

Not only that but if collaborators get the sense that we are going to shoe horn the spec in even it starts to effect moral.  It will also make some customers go ... hmmm maybe I'll skip Playstation 2 and just wait Playstation 3.

Lastly supposedly this has been in play for two years now.  So why is this stuff not ironed out?  The dream team is on the field and yet we are having a hell of a time getting a touch down.

-- 
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/509#issuecomment-266262811