Nemeski@lemm.ee to Technology@lemmy.worldEnglish · 4 个月前Google Chrome warns uBlock Origin may soon be disabledwww.bleepingcomputer.comexternal-linkmessage-square439fedilinkarrow-up11.02Karrow-down112cross-posted to: news@lemmy.linuxuserspace.showfirefox@lemmy.mltechnology@lemmy.zipbrowsers@lemmy.ml
arrow-up11.01Karrow-down1external-linkGoogle Chrome warns uBlock Origin may soon be disabledwww.bleepingcomputer.comNemeski@lemm.ee to Technology@lemmy.worldEnglish · 4 个月前message-square439fedilinkcross-posted to: news@lemmy.linuxuserspace.showfirefox@lemmy.mltechnology@lemmy.zipbrowsers@lemmy.ml
minus-squareAxum@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up3·4 个月前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.
minus-squareipkpjersi@lemmy.mllinkfedilinkEnglisharrow-up1·edit-24 个月前Those seem like really big hurdles. How can those be worked around? Is it not possible to trigger a manual block list update?
minus-squareAxum@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up1·4 个月前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.
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.