Comment

Comment on Google to weaken ad blockers on Chrome in a push for security

Evilcoleslaw@lemmy.world ⁨7⁩ ⁨months⁩ ago

As far as I know, the plan for Manifest V3 only included removing blocking from the WebRequest API and extensions using WebRequest could still see whatever activity they are given permission to view.

source

Sort:hotnew top

AProfessional@lemmy.world ⁨7⁩ ⁨months⁩ ago
Correct, and the reasoning for removing blocking was performance.

source
- TheDarkKnight@lemmy.world ⁨7⁩ ⁨months⁩ ago
  Wouldn’t loading the ads impact performance moreso than loading them? Not really a browser nerd so no idea it just seems like blocking a piece of content from loading outright would be less demanding than loading it.
  
  source
  - AProfessional@lemmy.world ⁨7⁩ ⁨months⁩ ago
    How the WebRequest API works is:
    
    Network process downloads data
    
    Sent to the WebExtension (delay #1)
    
    Extension runs arbitrary JavaScript (Slow to very slow)
    
    Results eventually make it to the WebProcess where it belongs.
    
    This is slow and will always be. Their change to remove blocking turns step 2/3 into a copy of the data, not a blocking call.
    
    Now an ad can be slower, just by more data or bad JS. But that isn’t Googles concern because they sell those ads.
    
    source
    TheDarkKnight@lemmy.world ⁨7⁩ ⁨months⁩ ago
    Ahhhh gotcha, thanks!
    
    source