> I use a variation of (2) today, but usually a subset of the element's stylesheet will suffice. If the element has some content in shadow root, there is no style I could provide to mock it. Also even, if I could it means I need to create and maintain `:not(:defined)` version of each and every third party custom element I use, what I believe, is not acceptable for any bigger project. > Since we are already inside of modules at this point you have to solve this regardless of whether you are using HTML modules or JavaScript modules to load your element definitions. With HTML Imports I don't have to solve this. In general, I found render-blocking feature of `link rel="import"` a great advantage, as I could load crucial dependencies up front. In the same fashion I provide crucial style sheet, I provide crucial custom elements definitions. Then, I could preload ones I may need later, and defer loading only those less important/not needed for the first paint. -- 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/645#issuecomment-433168998
Received on Thursday, 25 October 2018 19:04:45 UTC