tree d25e4bba1cd173cd556b9dbd8e909e1c53819f14
parent a2108adbb566d81747c4f906cfd93d2b238fe6b2
author Anders Hartvoll Ruud <andruud@chromium.org> 1615935517 -0700
committer Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> 1615936844 -0700

Make custom properties that are IACVT guaranteed-invalid (II)

Per recent spec change [1], custom properties that are invalid at
computed-value time (IACVT) shall become guaranteed-invalid [2]
if the custom property supports guaranteed-invalid values.

In order to maintain our current animations behavior related to cycles
(see CSSVarCycleInterpolationType), we still need to be able to
distinguish between "cyclic" and "invalid for other reasons" from the
outside. These two situations are now represented by
CSSCyclicVariableValue and CSSInvalidVariableValue, respectively.

[1] https://github.com/w3c/csswg-drafts/pull/6006
[2] https://drafts.csswg.org/css-variables/#guaranteed-invalid-value

Fixed: 1110188
I2S: https://groups.google.com/a/chromium.org/g/blink-dev/c/0xrbzYe_vxU/m/7bsL76n9CgAJ
Change-Id: I0e7b529e4ae595c6c327c45b4da1a43be64c1c88
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2762156
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#863497}