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).
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.
I have an extension with a small user base that uses 'declarativeNetRequestFeedback' permission. I haven't experienced any issue with the review process.
