Skip to content

update cookie block errors #41597

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Oct 20, 2025
+7 −11
Merged

update cookie block errors #41597

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
edd9d52
update cookie block errors
PassionPenguin Oct 20, 2025
d7cf20c
Apply suggestions from code review
PassionPenguin Oct 20, 2025
9fefda6
Apply suggestions from code review
PassionPenguin Oct 20, 2025
8e7aacf
Update index.md
PassionPenguin Oct 20, 2025
eaa94df
Make managing permissions instruction all one line
chrisdavidmills Oct 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...en-us/web/privacy/guides/storage_access_policy/errors/cookieblockedall/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,12 +19,12 @@ CookieBlockedAll=Request to access cookies or storage on "X" was blocked because

The permission can be changed or removed by:

- Going to _Preferences > Content Blocking_
- Going to _Settings > Privacy & Security > Enhanced Tracking Protection_.
- In the _Custom_ Content Blocking section, selecting a value other than _All Cookies_ for the _Cookies_ item

If the resource that is being blocked doesn't need authentication, you can fix the warning message by adding a `crossorigin="anonymous"` attribute to your element.

## See also

- [Content blocking](https://support.mozilla.org/en-US/kb/content-blocking) on [support.mozilla.org](https://support.mozilla.org/)
- [Enhanced Tracking Protection in Firefox for desktop](https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-deskto) on [support.mozilla.org](https://support.mozilla.org/)
- [The `crossorigin` attribute](/en-US/docs/Web/HTML/Reference/Attributes/crossorigin)
6 changes: 3 additions & 3 deletions .../privacy/guides/storage_access_policy/errors/cookieblockedbypermission/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,9 @@ CookieBlockedByPermission=Request to access cookies or storage on "X" was blocke

The permission can be changed or removed by:

- Going to _Preferences > Content Blocking > Cookies and Site Data_
- Clicking on the _Manage Permissions_ button and updating the listed exceptions
- Going to _Settings > Privacy & Security > Cookies and Site Data_.
- Clicking on the _Manage exceptions_ button and updating the listed exceptions.

## See also

- [Content blocking](https://support.mozilla.org/en-US/kb/content-blocking) on [support.mozilla.org](https://support.mozilla.org/)
- [Enhanced Tracking Protection in Firefox for desktop](https://support.mozilla.org/en-US/kb/content-blocking) on [support.mozilla.org](https://support.mozilla.org/)
8 changes: 2 additions & 6 deletions ...s/web/privacy/guides/storage_access_policy/errors/cookieblockedforeign/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,15 +17,11 @@ CookieBlockedForeign=Request to access cookies or storage on "X" was blocked bec

## What can be done

The permission can be changed or removed by:

- Going to _Preferences > Content Blocking_ and either
- adding an exception with the _Manage Exceptions_… button
- choosing the _Custom_ Content Blocking and unchecking the _Cookies_ checkbox
The permission can be changed or removed by going to _Settings > Privacy & Security > Enhanced Tracking Protection_ and adding an exception with the _Manage Exceptions_… button.

If the resource that is being blocked doesn't need authentication, you can fix the warning message by adding a `crossorigin="anonymous"` attribute to the relevant element.

## See also

- [Content blocking](https://support.mozilla.org/en-US/kb/content-blocking) on [support.mozilla.org](https://support.mozilla.org/)
- [Enhanced Tracking Protection in Firefox for desktop](https://support.mozilla.org/en-US/kb/content-blocking) on [support.mozilla.org](https://support.mozilla.org/)
- [The `crossorigin` attribute](/en-US/docs/Web/HTML/Reference/Attributes/crossorigin)
Loading