Update header name to Sec-CH-Device-Memory#51
Merged
tunetheweb merged 1 commit intomainfrom Dec 11, 2025
Merged
Conversation
miketaylr
approved these changes
Dec 11, 2025
Member
|
Changing the repo name doesn't seem that useful. Or the spec, since there's a JS API as well. |
Member
Author
|
Ah true. I'm gonna add an update to the Abstract in a separate PR:
As that's quite confusing! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes spec to the standardised Client Hints header format.
This was already changed in Chrome 97 which is the only implementation.
I'm not sure if the spec's name itself should also be changed? And if that requires any sort of W3C input to do this and/or a repo rename? Do you know @yoavweiss ? So for now I've only done' the Header field name.