- Joined
- Aug 20, 2006
- Messages
- 13,000
Ad-blocker developers (and users) can rest easy, as Google has decided to revise its collection of changes to the Chrome extensions platform. “Manifest V3” would have killed uBlock, Ghostery, and similar extensions by disallowing them from querying remotely hosted code via traditional APIs, but Google has had a change of heart due to backlash and new data suggesting ad-blocking requests didn’t have a significant effect on browser performance.
Chrome engineers justified the change by citing the performance impact of not having a maximum value for the number of network requests an extension could access. But the Ghostery team disagreed with this assessment. "From the measurements, we do not think this claim holds, as all popular content-blockers are already very efficient and should not incur any noticeable slow-down for users.” Their study found sub-millisecond median decision times per request, showing quite the opposite of what the Chrome team claimed.
Chrome engineers justified the change by citing the performance impact of not having a maximum value for the number of network requests an extension could access. But the Ghostery team disagreed with this assessment. "From the measurements, we do not think this claim holds, as all popular content-blockers are already very efficient and should not incur any noticeable slow-down for users.” Their study found sub-millisecond median decision times per request, showing quite the opposite of what the Chrome team claimed.