We are running into this with [Livemarks](https://addons.mozilla.org/en-US/firefox/addon/livemarks), a recommended extension. We already request `permission: ["<all_urls>"]`, because we want to be able to handle opening RSS URLs like https://magic.wizards.com/en/rss/rss.xml by showing a preview. For some RSS feeds however this doesn't work like [Gmail](https://mail.google.com/mail/u/0/feed/atom) or Reddit. We get an error message like: >Request to access cookie or storage on “https://mail.google.com/mail/u/0/feed/atom” was blocked because it came from a tracker and content blocking is enabled. To give our users a chance to add these RSS feeds my idea was to extend our code for manually adding RSS feed URLs by first requesting the appropriate permission like `browser.permissions.request({origins: ["https://mail.google.com/"]})`. Now we come back to this bug: Firefox always resolves this request to `true` and doesn't ask the users for permission and of course doesn't add the more specific host permissions that we need to bypass the cookie/storage blocking.
Bug 1502987 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We are running into this with [Livemarks](https://addons.mozilla.org/en-US/firefox/addon/livemarks), a recommended extension. We already request `permission: ["<all_urls>"]`, because we want to be able to handle opening RSS URLs like https://magic.wizards.com/en/rss/rss.xml by showing a preview. For some RSS feeds however this doesn't work like [Gmail](https://mail.google.com/mail/u/0/feed/atom) or Reddit. We get an error message like: >Request to access cookie or storage on “https://mail.google.com/mail/u/0/feed/atom” was blocked because it came from a tracker and content blocking is enabled. To give our users a chance to add these RSS feeds my idea was to extend our code for manually adding RSS feed URLs by first requesting the appropriate permission like `browser.permissions.request({origins: ["https://mail.google.com/"]})`. Now we come back to this bug: Firefox always resolves this request to `true` and doesn't ask the user for permission and of course doesn't add the more specific host permissions that we need to bypass the cookie/storage blocking.