←back to thread

"Begin disabling installed extensions still using Manifest V2 in Chrome stable"

(developer.chrome.com)
552 points freedomben | 4 comments | 11 Oct 24 14:20 UTC | HN request time: 0.829s | source
Show context
Mrdarknezz ◴[11 Oct 24 14:51 UTC] No.41809991[source]▶
Totally unrelated, firefox is an excellent browser
replies(2): >>41810027 #>>41813212 #
1. zb3 ◴[11 Oct 24 20:11 UTC] No.41813212[source]▶
But not when you want to install GrapheneOS using the web-based installer, because Mozilla refuses to implement WebUSB
replies(1): >>41815498 #
2. contravariant ◴[12 Oct 24 01:12 UTC] No.41815498[source]▶
Sounds like a reasonable trade-off.

I imagine they couldn't figure out what an appropriate warning window would look like for that kind of protocol.

replies(1): >>41817372 #
3. teruakohatu ◴[12 Oct 24 08:12 UTC] No.41817372[source]▶
Chrome supports WebUSB. The bowser asks if you want to connect a device and presents a list of supported devices. It works amazingly well.
replies(1): >>41847370 #
4. account42 ◴[15 Oct 24 11:23 UTC] No.41847370{3}[source]▶
So the user can be trusted to allow arbitrary websites raw access to potentially sensitive USB devices but cannot be trusted to give extensions the required access to fully block ads?