Bugzilla

Thanks very much Zach!

FYI  In addition to the release note,  I ended up  adding notes to `Refresh` and `Referrer` headers in https://github.com/mdn/content/pull/38190 on the basis that this is where you might look as a reader to understand when the referrer might be sent. 

I didn't include a note in the  `Referrer-Policy` doc for the same reason - the policy might prevent information being included in the referer after a refresh, but I don't think people would check it to find out what is going on "first". It also doesn't fit with the other information in that page. You might have other reasons for suggesting this that I've missed - in which case, perhaps propose some text.

Note also that I didn't add any detail on the same-page refresh. That doesn't seem to be causing the same level of problem for users, and it can wait until there is a resolution of the compat issue.

Thanks very much Zach!

FYI  In addition to the release note,  I ended up  adding notes to `Refresh` and `Referrer` headers in https://github.com/mdn/content/pull/38190 on the basis that this is where you might look as a reader to understand when the referrer might be sent. 

I didn't include a note in the  `Referrer-Policy` doc for the same reason - the policy might prevent information being included in the referer after a refresh, but I don't think people would check it to find out what is going on "first". It also doesn't fit with the other information in that page. You might have other reasons for suggesting this that I've missed - in which case, perhaps propose some text.

Note also that I didn't add any detail on the same-page refresh compatibility issue. That doesn't seem to be causing the same level of problem for users, and it can wait until there is a resolution of the compat issue.