Re: [w3c/webcomponents] has="mixin this, mixin that" (#663)

@annevk that sounds completely fair. What if, rather than specifying a particular mixin syntax or anything, we could just open up and generalise the Element Upgrade process - so that we could upgrade new prototypes as we needed?

Realise this is touching on #620, which is closed due to existence of `setPrototypeOf` / `__proto__` but as noted, they ruin engine optimisations, and this idea of dynamic Element Upgrades would also include lifecycle hooks e.g. connected / disconnected etc. I'm not sure if implementing it natively would fix those engine optimisation issues...?


-- 
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/663#issuecomment-327717546