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

I was warming up to the something-that-throws-outside-the-constructor idea (my bikeshed was `window.customElements.createInternals(this)`) but I can't figure out how to make it work. We have no ability to run code after element construction in the `new XElement()` case. There the only code we run is inside [HTMLConstructor], i.e. the `super()` call. So we have no way to flip a flag that says "can no longer use the thing".

In other words, if we want `new XElement()` to continue to work, I can't see how we'd be able to turn on access to the thing only inside constructors.

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