Re: [w3c/webcomponents] Repurposing the is="" attribute to allow multiple behaviors to be attached to a given element (#662)

I don't want to come off as cynical, but you do realize that the current spec is based on decades worth proto-specification [1] which after an all out and *still* unfinished interstellar war between browser vendors has culminated in the `is` attribute as we know it today? Even if it was still up for discussion, which I guess is fair and right, your specific suggestion would break the web in production, so why not ask instead: If Vue or some other framework can provide the developer experience you enjoy today, and without using Custom Elements, why should the spec be changed to emulate this pattern? It is always the frameworks job to provide an awesome API for folks building websites while it is the specifications job to provide a tedious API for folks building frameworks, which is different. In my unaffiliated opinion, the `is` attribute should only be changed at this late stage if it prevents you somehow from building a component based framework that can work just like you imagine. You also wouldn't change how `appendChild` and `insertBefore` works just because React provides a cooler API for generating DOM structure.

[1] See https://www.w3.org/TR/sXBL/ and https://www.w3.org/TR/xbl/ and https://msdn.microsoft.com/en-us/library/ms531079(v=vs.85).aspx 

-- 
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/662#issuecomment-327515695