4 ms·
One issue I have with this is that I won’t be able to apply a userstyle to restyle a page anymore, and I won’t be able to use websites without JS anymore. Just
by kuschku 11y ago
One issue I have with this is that I won’t be able to apply a userstyle to restyle a page anymore, and I won’t be able to use websites without JS anymore.
Just earlier today I had an issue where I was trying to read this article [1] and the page, after loading for around 3 minutes (I was on mobile and on the free plan of my ISP, which gives only 64kbps, but unlimited), had all the content, but neither JS nor CSS.
There are already many websites which I can’t use at all anymore because they make everything invisible until JS and CSS are loaded. Flash of unstyled content is not an issue for me, it’s the whole reason I am able to read pages.
[1] http://www.npr.org/2015/10/22/450583840/in-d-c-and-china-two-approaches-to-a-streetcar-unconstrained-by-wires http://www.npr.org/2015/10/22/450583840/in-d-c-and-china-two...
- aaronharnly 11y ago> One issue I have with this is that I won’t be able to apply a userstyle to restyle a page anymore With the caveat that I only sorta understand this stuff -- if it emerges this way after the politics & process, you should be able to use the 'deep combinator' >>> to apply styles even across shadow DOM boundaries. https://drafts.csswg.org/css-scoping-1/#deep-combinator https://drafts.csswg.org/css-scoping-1/#deep-combinator
- kuschku 11y ago> It’s currently disputed whether this combinator should exist. Also, it breaks about every existing userstyle, ever. And there should be a more general solution that also handles the shadow DOM of browser-internal elements like the <input type="file">
- colordrops 11y agoI think the deep combinator is already deprecated in Chrome and unlikely to make it into the spec.
- Touche 11y agoThis is not an issue you have with WebComponents specifically but the direction the web has been taking for the last 10 years.
- deleted 11y ago[deleted]