3 ms·
Definitely agree, not a fan of the permissions. The broad permissions were required from a usability standpoint. Granting permission on every site for this ext
by mitch292 1y ago
Definitely agree, not a fan of the permissions.
The broad permissions were required from a usability standpoint. Granting permission on every site for this extension would just be a 1 to 1 replacement of clicking reject on the banner or pop up for every site.
I would hope that before Chrome approves an extension to be added to the store that they are auditing the content of package.
- deleted 1y ago[deleted]
- shadowgovt 1y agoOne of the reasons Manifest v3 was started is that is impossible for an extension that eval's arbitrary code from the web (or downloads, say, a dynamic list of data and acts on it). For something like this, it's tractable.
- dhc02 1y agoPersonally, I would still love a site-by-site "reject non-essential cookies" prompt from an extension that's in the same place, with the same UI, on every site. Still a click, but lots better than having to figure out how to accomplish it on each and every site.
- larusso 1y agoExactly. The biggest pain is to read and figure out what the next button actually does. Is the big Button an except all? Use selected? Or what ever wording they use. I might not want to block cookies for certain pages. So an extension that finally creates this single UX flow would be very helpful indeed.
- cies 1y agoExactly. So you could have 2 shortcuts: one for reject all non essential, one for accept all. Much better UX than figuring out per site which button to click.
- randunel 1y agoWhy would you ever accept all? The options should be reject all non essential and reject all (may break something)
- groby_b 1y agohttps://developer.chrome.com/docs/webstore/review-process https://developer.chrome.com/docs/webstore/review-process