We have two new posts out today addressing the confusion and misinformation surrounding what Chrome is doing with extensions. This first one gives context on the broader security, privacy and abuse considerations we're addressing.https://security.googleblog.com/2019/06/improving-security-and-privacy-for.html …
-
-
I know that major API changes are always a pain for developers and they would rather not have to deal with them, but please keep in mind stats like "42% of malicious extensions use the Web Request API" when you're considering what we're trying to improve here.
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
If the WebRequest API is so bad for privacy that it needs to be killed, why am I still able to emulate it with ServiceWorkers? Chrome extensions can inject content scripts that register generated ServiceWorkers which can serve as a proxy interface for an emulated WebRequest API.
-
That's not how service workers work in extensions. An extension's SW can only intercept requests to it's own domain (e.g. chrome-extension://abcdefg/index.html)
- Još 9 drugih odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.