If I have a page like this... <element-with-shadow-dom/> the no-JS version (which is also the SSR'd page, until your JS loads and inits) looks totally different from how it should, unless there's a declarative way of specifying the shadow DOM styles and content
-
-
You could. But I don't want to spend my time setting up Rendertron, and I don't want to spend my time designing placeholder CSS, and since I don't need to (because of UI frameworks) I'm not going to! *That's* the bar — it has to be as easy or easier than the tools people use
-
Again, this is coming from someone who definitely *doesn't* consider themselves part of the JS industrial complex — I want to align with the platform to the greatest extent possible. But right now, CEs and SD only create problems for me, they don't solve them
- 4 more replies
New conversation -
-
-
I am not sure I agree. If we want to keep _something sane_ on the page when JS is disabled/broken (or even *gasp* keep the app working thru SSR), you can only do the whole placeholder-CSS thing. That’s far from ideal and gets virtually impossible to do when you embrace slots.
-
Agreed. This is an extremely challenging problem.
End of conversation
New conversation -
-
-
Rendertron is way resource consuming and expensive last time I head
-
My preferred analogy for running a headless browser for the sake of SSR: it's like going to the shop and buying a fruitcake and pulling out all of the raisins, instead of just buying some raisins
- 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.