Re: [whatwg/dom] Declarative Shadow DOM (#510)

"disappearing" makes it also problematic to implement a inter-operable custom element polyfill as stated https://github.com/whatwg/html/issues/4566

I think the main concern and reason was the memory usage https://github.com/whatwg/dom/issues/510#issuecomment-329349780.

Maybe to address also https://github.com/whatwg/dom/issues/510#issuecomment-372224104
> The proposed semantics of shadow element has this problematic behavior (since shadow isn't a real element).

we could keep `<shadowroot>` element there as we keep `<template>`. Just make it so it does not have `.children`. Maybe we could keep `hostElement.shadowRoot === hostElement.querySelector('shadowroot').content` for open shadows, and both `null` for closed.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/510#issuecomment-486524288

Received on Thursday, 25 April 2019 05:26:34 UTC