Re: [w3c/webcomponents] Add Declarative Shadow DOM strawman proposal (#731)

@matthewp 
> I believe you are saying that `<fancy-content>` might exhibit a FOUC. 

I'd say FOUC is a result of the post-creation upgrade of `<fancy-content>` from either incomplete or leaky HTML&CSS. 

In the JS-enabled environment, with custom element definition already loaded there is no FOUC - see http://jsbin.com/rivoyiz/edit?html,output. Could you make this element be rendered without a FOUC in JS-free environment, and still use same id attributes and scoped styles?

I was not able to do so, that's why I propose `<shadowroot>` that could be used like that http://jsbin.com/gequvih/2/edit?html,output Please note, that light and shadow DOM are exactly 1:1.

Currently, you cannot server-side render it without side effects:
- FOUC,
- leaky styles,
- avoiding actual Shadow DOM features.

> The solution is the same as what you do for CSS; you inline essential code into the head.

But in that case, the code we need to inline into the head is the JavaScript, what is against the requirements. 

-- 
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/pull/731#issuecomment-363924516