- From: Mason Freed <notifications@github.com>
- Date: Mon, 31 Aug 2020 12:04:57 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 31 August 2020 19:05:12 UTC
> Oh right. I was thinking of the synchronous construction case only. We probably need to introduce a new custom element state like "precustomized" and set to it right before step 8.2 ("Let constructResult be the result of constructing C, with no arguments.") of [upgrading an element](https://html.spec.whatwg.org/multipage/custom-elements.html#concept-upgrade-an-element). Then the change I'm suggesting will check whether the custom element state is either `custom` or `precustomzied`. After re-reading [Upgrade an element](https://html.spec.whatwg.org/multipage/custom-elements.html#concept-upgrade-an-element) a few times, I think the above suggestion sounds like it'll work. If there's general agreement here, I'm happy to put together a spec PR, and modify the Chromium implementation. Any objections? @domenic? -- 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/871#issuecomment-683971426
Received on Monday, 31 August 2020 19:05:12 UTC