3 ms·

It's currently under review because it's using the chrome.declarativeNetRequest (same API uBlock is using)

cal85 3y ago
Hang on do you mean to say the web store might accept an extension with `declarativeNetRequestFeedback` permission, it just might take longer and be less certain? I've got an extension that could potentially really benefit from using this permission (because I want to be able to dynamically decide whether to take an action in a content script based on the `Content-Type` header; currently I use imperfect content-sniffing heuristics instead). The last time I dug into it, it seemed that this permission just wasn't going to be available after the Manifest v3 moratorium that has already passed. So I'm interested to know if anything has changed (or if there's any special way that extensions can be approved with this permission, e.g. if they're popular enough and have a good privacy track record).
- npace12 3y ago
  I'm not sure, but I was curious too, so I submitted it for review to find out.
  - cal85 3y ago
    Interesting, I had assumed it wouldn't even allow uploading it if the manifest required that permission. Hope they allow it for you!
    - npace12 3y ago
      It got rejected today but not due to the permission, I'll pretty it up and try again. Violation reference ID: Yellow Zinc Violation: Description provided is insufficient to understand the functionality of the item.
      - cal85 3y ago
        Appreciate you keeping me posted, please comment again when your next attempt gets approved/rejected!
        npace12 3y ago
        Managed to get it in! [1] I added ability to do blocking and made the "management" and "declarativeNetRequestFeedback" permissions optional, requested via a button on the popup page. While declarativeNetRequestFeedback works when you install it manually, the store version tells you the permissions are there, but chrome.declarativeNetRequest.onRuleMatchedDebug is undefined, so unfortunately, the store version can't count the number of requests. Blocking still works though, just you don't get any feedback about what's blocked. I think this is still useful to be able to block extensions, so I'll keep carrying 2 versions, 1 for the store with limited functionaly. 1: https://chrome.google.com/webstore/detail/little-rat/oiopkpalpilladnibecobcecijffaflf https://chrome.google.com/webstore/detail/little-rat/oiopkpa...
- deleted 3y ago
  [deleted]
- ris58h 3y ago
  I have an extension with a small user base that uses 'declarativeNetRequestFeedback' permission. I haven't experienced any issue with the review process. https://ris58h.github.io/youtube-chapters-in-player/ https://ris58h.github.io/youtube-chapters-in-player/
  - npace12 3y ago
    Your extension is not actually using declarativeNetRequestFeedback, though.
p1mrx 3y ago
Isn't declarativeNetRequest the new, less powerful Manifest V3 API that uBlock Origin Lite is using?
- npace12 3y ago
  yeah, little rat is using manifest v3

Hang on do you mean to say the web store might accept an extension with `declarativeNetRequestFeedback` permission, it just might take longer and be less certain? I've got an extension that could potentially really benefit from using this permission (because I want to be able to dynamically decide whether to take an action in a content script based on the `Content-Type` header; currently I use imperfect content-sniffing heuristics instead). The last time I dug into it, it seemed that this permission just wasn't going to be available after the Manifest v3 moratorium that has already passed. So I'm interested to know if anything has changed (or if there's any special way that extensions can be approved with this permission, e.g. if they're popular enough and have a good privacy track record).

npace12 3y ago
I'm not sure, but I was curious too, so I submitted it for review to find out.
- cal85 3y ago
  Interesting, I had assumed it wouldn't even allow uploading it if the manifest required that permission. Hope they allow it for you!
  - npace12 3y ago
    It got rejected today but not due to the permission, I'll pretty it up and try again. Violation reference ID: Yellow Zinc Violation: Description provided is insufficient to understand the functionality of the item.
    - cal85 3y ago
      Appreciate you keeping me posted, please comment again when your next attempt gets approved/rejected!
      - npace12 3y ago
        Managed to get it in! [1] I added ability to do blocking and made the "management" and "declarativeNetRequestFeedback" permissions optional, requested via a button on the popup page. While declarativeNetRequestFeedback works when you install it manually, the store version tells you the permissions are there, but chrome.declarativeNetRequest.onRuleMatchedDebug is undefined, so unfortunately, the store version can't count the number of requests. Blocking still works though, just you don't get any feedback about what's blocked. I think this is still useful to be able to block extensions, so I'll keep carrying 2 versions, 1 for the store with limited functionaly. 1: https://chrome.google.com/webstore/detail/little-rat/oiopkpalpilladnibecobcecijffaflf https://chrome.google.com/webstore/detail/little-rat/oiopkpa...
deleted 3y ago
[deleted]
ris58h 3y ago
I have an extension with a small user base that uses 'declarativeNetRequestFeedback' permission. I haven't experienced any issue with the review process. https://ris58h.github.io/youtube-chapters-in-player/ https://ris58h.github.io/youtube-chapters-in-player/
- npace12 3y ago
  Your extension is not actually using declarativeNetRequestFeedback, though.

p1mrx 3y ago

Isn't declarativeNetRequest the new, less powerful Manifest V3 API that uBlock Origin Lite is using?

npace12 3y ago
yeah, little rat is using manifest v3