Nemeski to Technology@lemmy.worldEnglish • 4 months agoGoogle Chrome warns uBlock Origin may soon be disabledwww.bleepingcomputer.commessage-square447fedilinkarrow-up11.03Kcross-posted to: news@lemmy.linuxuserspace.showfirefox@lemmy.mltechnology@lemmy.zipbrowsers@lemmy.mltechnology@lemmit.online
arrow-up11.03Kexternal-linkGoogle Chrome warns uBlock Origin may soon be disabledwww.bleepingcomputer.comNemeski to Technology@lemmy.worldEnglish • 4 months agomessage-square447fedilinkcross-posted to: news@lemmy.linuxuserspace.showfirefox@lemmy.mltechnology@lemmy.zipbrowsers@lemmy.mltechnology@lemmit.online
minus-squareAxumlinkfedilinkEnglish3•4 months agoThe ‘block element’ picker is the big one that can not be implemented in the lite version. Also included block lists can’t update unless the extension itself updates.
minus-square@ipkpjersi@lemmy.mllinkfedilinkEnglish1•edit-24 months agoThose seem like really big hurdles. How can those be worked around? Is it not possible to trigger a manual block list update?
minus-squareAxumlinkfedilinkEnglish1•4 months agoIt’s not something that can be worked around. It’s specifically a design feature of manifest v3 to restrict these types of things. Your options are to accept this or use a different browser.
The ‘block element’ picker is the big one that can not be implemented in the lite version.
Also included block lists can’t update unless the extension itself updates.
Those seem like really big hurdles. How can those be worked around?
Is it not possible to trigger a manual block list update?
It’s not something that can be worked around. It’s specifically a design feature of manifest v3 to restrict these types of things.
Your options are to accept this or use a different browser.