Stanislav Lashmanov

Thank you @annevk! This makes sense, sorry for not paying attention to the FAQ first, I've tried to address your concern.

@keithamus good point! The problem with this solution is that you basically have to wrap your whole app within a Web Component and you also have to know where to...

> Could you describe some of these? @keithamus the main issue is styling. You have to put your primary content into a `` element in order to declare slots deep...

@keithamus how you define deep slots outside of shadow root? This won't work: ```html The rest of my web page goes here new content gets streamed out-of-order! ``` You have...

@keithamus this only works if you place the slotted content within the wrapper element, which defeats the purpose. This now becomes a blocking operation: we can't continue streaming the rest...

There are two ways that you can render Declarative Shadow DOM (DSD) on the page: 1. As part of a document HTML 2. Using JavaScript and `Document.parseHTMLUnsafe()` (which is an...

I have originally wanted to post in #43, but this discussion seems to be a more approprate place for that. ---- The spec is kind of uncertain in the regard...

> You're in luck! Sec-CH-Viewport-Width already exists. The other currently defined hints are in Client Hints Infrastructure, this repo is strictly hints that mimic the User Agent string in functionality....

> Sec-CH-Viewport-Width is already available in Chrome. Could I ask you to point to the specific page where I can verify that? Because my current Chrome installation doesn't send it...

> If you include Sec-CH-Viewport-Width in your Accept-CH header, then on the next request to the same origin, Chrome will include the Sec-CH-Viewport-Width header. That is the problem here. Negotiable...