Chrome 119-121 had partial relative oklab()
/oklch()
support
#26551
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
As noted in the linked issue, this mostly copies the partial support notes for relative
rgb()
,hsl()
, andhwb()
in certain Chrome versions to document a very similar incorrect channel serialization range in relativeoklab()
/oklch()
.Test results and supporting details
Code used and per-browser-version results are commented in the linked issue: #26041 (comment). I observed the erroneous behavior in Chromium 121, but not 122.
I'm not familiar enough with the Chromium bug tracker to find if there's a bug that should be linked here. (I wouldn't be surprised if it was fixed with the relativeFound using bisect-builds.py; will update link.rgb()
bug, which links to https://crbug.com/41490327.)Related issues
Resolves #26041.