5 ms·
Can any extension still be able to read my browsing history? IE. know what URLs I visit. What Google searches I perform? Even if it's technically harder to impl
by AznHisoka 7y ago
Can any extension still be able to read my browsing history? IE. know what URLs I visit. What Google searches I perform? Even if it's technically harder to implement.
If so, then I totally agree: this change does absolutely nothing! But as expected from Google: this sort of thing has been going on for 5-10 years, and nothing has been done. They got my hopes up yet again.
- danShumway 7y agoShort answer yes.[0] > In Manifest V3, this API will be discouraged (and likely limited) in its blocking form. The non-blocking implementation of the webRequest API, which allows extensions to observe network requests, but not modify, redirect, or block them (and thus doesn't prevent Chrome from continuing to process the request) will not be discouraged. Longer answer, there are multiple good changes coming in V3 (in particular, the introduction of active-tab permissions, which would let you have an extension that can only run code when you explicitly click on it), but those changes aren't really part of the blocking/observation argument that's been happening. I thought about doing a blog post going into more detail about this at one point, but I figured it was unlikely to make anything change, and that the controversy was old enough that anyone who wasn't already informed wouldn't care any more. If I'm wrong, maybe I should take a week and write something more detailed. [0]: https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3NzzhHzc-qnk4w4PX-0XMw8/edit# https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3Nzz...