Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bug 1623347 [wpt PR 22318] - [css-variables] Custom props with invali…
…d var() should behave as 'unset', a=testonly Automatic update from web-platform-tests [css-variables] Custom props with invalid var() should behave as 'unset' We currently have a (WPT-enforced) bug where custom properties that reference guaranteed-invalid values [1] behave themselves as guaranteed- invalid. This is not correct per spec, which requires the custom property to behave as 'unset' in this case. This was clarified in [2], although the spec has described this behavior long before that. Unfortunately Firefox has the same issue. Safari on the other hand, does implement it correctly. [1] https://drafts.csswg.org/css-variables/#guaranteed-invalid [2] w3c/csswg-drafts#4075 Bug: 980930 Change-Id: I84a0da3aad6b72b574009d560eb868632769098a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108026 Commit-Queue: Anders Hartvoll Ruud <andruudchromium.org> Reviewed-by: Xiaocheng Hu <xiaochenghchromium.org> Cr-Commit-Position: refs/heads/master{#751636} -- wpt-commits: fc793094912b67b45a94d101819bffb9b9307710 wpt-pr: 22318 UltraBlame original commit: aaae9e1c209687addde4400f03ab390667307b15
- Loading branch information