Chrome 144 adds ch-ua-high-entropy-values permission#28895
Merged
chrisdavidmills merged 9 commits intomdn:mainfrom Feb 2, 2026
Merged
Chrome 144 adds ch-ua-high-entropy-values permission#28895chrisdavidmills merged 9 commits intomdn:mainfrom
ch-ua-high-entropy-values permission#28895chrisdavidmills merged 9 commits intomdn:mainfrom
Conversation
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
caugner
requested changes
Jan 23, 2026
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
caugner
approved these changes
Jan 30, 2026
api/NavigatorUAData.json
Outdated
| "chrome": { | ||
| "version_added": "90" | ||
| "version_added": "90", | ||
| "notes": "From Chrome 144, whether this feature returns high-entropy values can be controlled with the `ch-ua-high-entropy-values` permissions policy." |
Contributor
There was a problem hiding this comment.
Nit: Should we be explicit?
Suggested change
| "notes": "From Chrome 144, whether this feature returns high-entropy values can be controlled with the `ch-ua-high-entropy-values` permissions policy." | |
| "notes": "Before Chrome 144, the method always returns high-entropy values. From Chrome 144, this can be controlled using the `ch-ua-high-entropy-values` permission." |
Contributor
Author
There was a problem hiding this comment.
This is not really true, though. If you don't specify any high entropy values to return (i.e., if the getHighEntropyValues() argument is given as an empty array), then it will return only low-entropy values. I think I will update my wording to "whether this method can", or similar.
ch-ua-high-entropy-values permission
ch-ua-high-entropy-values permissionch-ua-high-entropy-values permission
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.
Summary
Chrome 144 adds support for the
ch-ua-high-entropy-valuesPermissions-Policydirective. See https://chromestatus.com/feature/6176703867781120.This PR adds a data point for the feature itself, and a note to the
NavigatorUAData.getHighEntropyValues()data point to state that this feature can be controlled by the new policy.Test results and supporting details
Related issues