We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Incorrect support data (example: BrowserX says "86" but support was added in "40")
Per mdn/content#22266 (comment), it looks like Sec-CH-Save-Data doesn't actually exist, and what's actually shipped in https://chromestatus.com/feature/5645928215085056 is the change of the implementation of Save-Data and the addition of the CH-Save-Data permission policy.
Sec-CH-Save-Data
Save-Data
CH-Save-Data
No response
This entry removed, and possibly anything else relevant documented, like the new permission policy.
See https://chromestatus.com/feature/5645928215085056
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What type of issue is this?
Incorrect support data (example: BrowserX says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
Per mdn/content#22266 (comment), it looks like
Sec-CH-Save-Data
doesn't actually exist, and what's actually shipped in https://chromestatus.com/feature/5645928215085056 is the change of the implementation ofSave-Data
and the addition of theCH-Save-Data
permission policy.What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
This entry removed, and possibly anything else relevant documented, like the new permission policy.
Did you test this? If so, how?
See https://chromestatus.com/feature/5645928215085056
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
No response
Do you have anything more you want to share?
No response
MDN URL
No response
MDN metadata
No response
The text was updated successfully, but these errors were encountered: