![]() Will it impact other browsers in the same way? I mean, if there is no webRequest API that can be used, what could they possibly do except to rely on their own built-in ad-blockers? This got me wondering about what could happen when Google decides to kill support for v2 add-ons, and forces extensions to use Manifest V3. I will admit that I find it surprising that the removal of a simple feature in Chromium's source code impacts every browser that uses it as the base, do they have a choice? This does give Google an advantage over the competition. That said, if a malicious extension, toolbar or website, manages to use the add search engine option to inject a harmful search provider in the browser, and set it as the default provider, it wouldn't be stopped, would it? That is likely a very rare scenario, one that can easily be prevented by using an ad-blocker like uBlock Origin, avoiding illegal websites, and good old common sense of not clicking links randomly. ![]() It is a precautionary measure that could end up protecting the user in the event a malware tries to delete the default search engine, or hijack it. ![]() ![]() I think this change may not affect most users. You can still add custom search providers if you want to, and this allows you to edit the search parameters. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |