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

The main issue I have with PE as it is implement here is that it does handicap the solution / app.  The minute the client wants two more custom elements that collaborate in the page, the functionality implemented with the `is` attribute for the purpose of clients that need PE becomes useless.  So the client comes up to you and says "Hey can we add this and this and this to make the page really awesome!!??".  "Nop - sorry Ed - this is a PE App.  We've told you before and we'll tell you again NO awesome stuff!  Now go back to the lunch room and play pong.".

But why does it have to be like that?  The best possible solution we can imagine here will allow us to use any custom element and still achieve PE.  

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