Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758)

@trusktr thank you for the idea.

> then extend from it (assume the mixin extends HTMLElement by default):

The mixin needs to support not only HTMLElement but also any classes extending HTMLElement as a base class.  I have two concerns about it.

- Hard to standardize it because WebIDL is not capable to define such mixin.
- Implementability is questionable.  Usually web platform features are implemented at outside of a JavaScript engine.  I'm not sure if all UAs can provide such dynamic mixins with their JavaScript engines.   Actually I don't know whether it's implementable in Blink with V8 though I'm a Chrome engineer.




-- 
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/758#issuecomment-439825489