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

First of all let me say that these examples and articles are very cool.  I'm going to have to do a deep dive on these!

> What would is solve for them?
> It'd be a better way to bootstrap shaders without needing to pollute the global context with unique IDs all over.

This is a good point.  Definitely seems like we can do better here.  As you have probably noticed, I lean more to the dedicated custom element side, along with schema relaxations on the HTML spec so that we can place elements where we need to place elements, but this is the best example I have seen so far to convince me that `is` might actually be valuable.  Thanks.

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