[css-properties-values-api] Accept any value through setProperty. #18029
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.
According to a recent spec change, the syntax of a registered custom
property must be ignored until computed-value time. This means that
setProperty may not inspect the PropertyRegistry and reject values
based on that.
This CL also removes the PropertyRegistry parameter in many places, to
avoid incorrectly using it in the future.
Bug: 641877
Change-Id: I99c58775e800500862378420118d81fe3186e739
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1714590
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680388}