EXTREME CO-SIGN @chockenberry YOU HAVE MY AXE
“Bug 194028 - Add limits to the amount of JavaScript that can be loaded by a website” https://bugs.webkit.org/show_bug.cgi?id=194028 …
-
-
-
Replying to @beep @chockenberry
Go up north, spread worrrrd in the streets!
2 replies 0 retweets 4 likes -
I think
@slightlylate was once toying with this idea, but as far as I know nothing ever came of it. Not that this is a bad idea, mind you!1 reply 0 retweets 4 likes -
I'm still working on it: https://chromium-review.googlesource.com/c/chromium/src/+/1265506 …
2 replies 2 retweets 19 likes -
Replying to @slightlylate @ppk and
Current debate is on how to roll this out. I am proposing a MOAR-TLS-like approach wherein we try to limit damage by starting in high-value places (Search crawl, PWAs install criteria, Data-Saver mode) and limit to maintained sites (don't break legacy)
2 replies 1 retweet 10 likes -
Replying to @slightlylate @ppk and
It sounds like this is an automated approach (which is good.) What I'm talking about (and what we currently have with content blockers) is a more user-centric approach. Let the user decide how much JavaScript they want to load for a site.
2 replies 0 retweets 3 likes
Would love to discuss! All the numbers in my prototype are guesses, and no UI locked. Slider could be an option.
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.