News for hackers. Stuff that matters.
Re:Please consider not adopting Google WebComponents by gildas on Tuesday March 17, 2020 @10:37AM (#22605184)
Yes I'm sure. It was a bug in SingleFile [1] and to fix it (I'm the author), I must add a JavaScript script in the saved page to deserialize the shadow root contents that are missing. It means that JS is required to view this saved page correctly.

[1] https://github.com/gildas-lormeau/SingleFile

Re:Please consider not adopting Google WebComponents by rictic on Tuesday March 17, 2020 @02:32PM (#22608386)
Work is underway on speccing out declarative shadow doms, which would remove the need for that JS: https://github.com/mfreed7/declarative-shadow-dom
Re:Please consider not adopting Google WebComponents by mattnewton on Tuesday March 17, 2020 @11:29AM (#22605786)
I mean, JavaScript being required to view pages sounds like Pandora’s already opened box.
Re:Please consider not adopting Google WebComponents by gildas on Tuesday March 17, 2020 @11:37AM (#22605886)
I disagree, I develop SingleFile for 10 years. That's the first time I need to include a script in the saved page in order to display it properly. Until the existence of Web Components, JavaScript was not needed to display a saved page.

Edit: to be clear, saved pages are HTML snapshots, not full web apps stored in a page.