PSA re: the wild misreporting about Extensions Manifest v3: declarativeNetRequest *is a list-based blocker*, and that's what's being added. This is the same approach Apple/Safari uses for the same reasons (perf & privacy): https://developer.chrome.com/extensions/declarativeNetRequest …
-
-
There *are* open debates about various limits in the new declarative world. But saying "debates rage about the size of a number as tests to verify continue" isn't a great headline...soooo...
Show this thread -
For sense of scale for those just joining, Apple limits the total number of rules in the Safari implementation to 50K (if I understand it correctly; doesn't seem documented). Chrome's proposal is 30K *per extension* with evaluation ongoing to raise it: https://developer.chrome.com/extensions/declarativeNetRequest#property-MAX_NUMBER_OF_RULES …
Show this thread
End of conversation
New conversation -
-
-
What's the benefit for the user if the extensions "doesn't use a slower system" but then the page loads tons of JS and pegs the CPU?https://twitter.com/gorhill/status/1134127721427144705 …
-
So this is a numbers question and one that the team should absolutely share results on. I will however note that the assertion in this tweet also comes without data.
- 1 more reply
New conversation -
-
-
I don't think saying "Safari does it too!" is a great defense. Safari has the reputation as the worst modern browser, and least standards compliant. Developers hate Safari. So you want to be like Safari... why?
- 1 more reply
New conversation -
-
-
Have any benchmarks or evidence been provided that shows that existing blocking API is "slow" or "unsafe"?
- End of conversation
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.