Release Note Request (optional, but appreciated) [Why is this notable]: This is a rather big change that has potential web compatibility risks [Affects Firefox for Android]: No [Suggested wording]: OpaqueResponseBlocking is now enabled by default. [Links (documentation, blog post, etc)]: https://groups.google.com/a/mozilla.org/g/dev-platform/c/ROU9eDb8alY I guess if we want the wording to be more specific and descriptive, we could say "The responses of no-cors cross origin requests might be block to prevent attackers from reading them"? This should goes to 118 release note.
Bug 1851143 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Release Note Request (optional, but appreciated) [Why is this notable]: This is a rather big change that has potential web compatibility risks [Affects Firefox for Android]: No [Suggested wording]: OpaqueResponseBlocking is now enabled by default. [Links (documentation, blog post, etc)]: https://github.com/annevk/orb The `Intent to Ship` email might be helpful for drafting the wording: https://groups.google.com/a/mozilla.org/g/dev-platform/c/ROU9eDb8alY I guess if we want the wording to be more specific and descriptive, we could say "The responses of no-cors cross origin requests might be block to prevent attackers from reading them"? This should goes to 118 release note.