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

@tomalec these might be good reasons.  Lets do them one by one.

> you need element's specific parsing context (template, table, script, meta,... dozens of others) ,

Can you give me a simple real world example of when you need one of these and point out how it is better than using the corresponding custom element by itself?  BTW - I do understand that if you place a custom element within a table the browser will boot it.  But is that the only reason? 

@WebReflection also gave a really good example for shaders.  And I agree with him that in the current state of things `is` is useful in the context he gave.  But I still think we can do even better.  For example if we get a schema relaxtion switch so that we can place elements in table container then we can produce shaders in custom elements that are developer friendly and minimize project delivery time, browser lines of code, etc.

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