![]() ![]() Features like Offscreen Documents, improved service worker control, and content filtering support have been key focal points in narrowing the gap between Manifest V2 and V3.ĭespite Google's efforts to bridge functionality gaps and address concerns, the impending shutdown of Manifest V2 extensions, including uBlock Origin, has been a point of contention. The enhancements introduced aim to elevate the extension platform's capabilities while ensuring a more secure browsing environment. Google's commitment to privacy and security in Manifest V3 remains at the forefront of this transition. The transition timeline loomed, leaving many wondering about the future of their favorite ad-blocking extensions. Users and developers expressed concerns about potential limitations and the impact on their browsing experience. However, the path to Manifest V3 hasn't been without its challenges, especially concerning extensions like uBlock Origin. This interval allowed Google to refine Manifest V3, focusing on improving functionality and addressing migration concerns. The journey towards Manifest V3 commenced with Google's pause in the deprecation of Manifest V2, acknowledging and responding to the feedback from developers. It's a pivotal moment, and understanding the implications of this transition is crucial for users and developers alike. The confirmation that Manifest V2 extensions, including uBlock Origin, will be disabled in mid-2024 has sent ripples across the online community. However, recent news from Google regarding the transition to Manifest V3 spells a significant change for this beloved extension and others like it. Like a child, they want to break everyone else’s toys so all that’s left to play with is them.In the ever-evolving landscape of Chrome extensions, one tool has stood out for its prowess in blocking intrusive ads and maintaining user privacy: uBlock Origin. I do applaud Google for wanting to create a new standard for the types of ads we see, blocking overly intrusive ads by default and so forth.īut looking at the big picture, and recent changes, it seems that Google wants to make sure People don’t use their own ad-blockers anymore, and are forced to use Google’s version. This all fits nicely with recent developments at Google about Chrome coming up with its own ad-blocker while allowing for certain “acceptable ads”. This suggests that all current ad-blockers would be impacted. The changes are supposed to not only break popular extensions such as uBlock Origin as they work at the moment, but will make them unfeasible in the future because of limiting the amount of actions an ad-blocker can do to a page in a given time. If it were impacted, are the devs considering a way around this?.Is the ad-blocker in Brave implemented in such a way that this change would impact it?.Are the Brave development team aware of this change?.So if these changes make it to Chromium, they will come, in extension, to Brave and I fear that this might break its ad-blocker. ![]() ![]() I don’t see Google implementing the changes to Chrome without Chromium going through them first, since Chromium development is essentially Chrome development. Now, I understand that Brave isn’t Chromium and that Chromium isn’t Chrome.īut it should be in everybody’s interest that the Brave code stick as close as possible to the Chromium base, to benefit from the security, compatibility and up-to-dateness of Chromium.Īnd Chromium is, for all intents and purposes, a project that is both “open source” and, at the same time, completely under the control of the big G (just like Android, for that matter). Well, since ad-blocking is one of the essential features of Brave, and Brave is now forking Chromium, this might become an issue if Brave continues to implement changes made to Chromium. In a nutshell, the suggested change would break the functionality of most, if not all popular ad-blocker extensions in Chromium, which the developers of these extensions have been pointing out to the development team. There is a new discussion or issue in Google Chrome development about a proposed change to the extensions system in Google Chrome / Chromium development.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |