Files
ladybird/Tests/LibWeb/Text/expected/wpt-import/css/css-properties-values-api/var-reference-registered-properties.txt
Sam Atkins 61a0898f5f LibWeb/CSS: Stop inserting whitespace when serializing component values
Now that we don't remove whitespace when parsing, we don't need to
artificially insert it back in again when serializing. We do now need
to trim leading and trailing whitespace from UnresolvedStyleValues, as
this previously was done as part of the whitespace insertion.

This makes our serialization of UnresolvedStyleValues more correct and
gets us a few WPT passes for each property in the Typed OM tests.
2025-11-03 11:23:21 +00:00

22 lines
1.2 KiB
Plaintext

Harness status: OK
Found 16 tests
10 Pass
6 Fail
Fail var() references work with registered properties
Pass References to registered var()-properties work in registered lists
Pass References to mixed registered and unregistered var()-properties work in registered lists
Pass Registered lists may be concatenated
Fail Font-relative units are absolutized when substituting
Fail Calc expressions are resolved when substituting
Fail Lists with relative units are absolutized when substituting
Fail Values are absolutized when substituting into properties with universal syntax
Fail Invalid values for registered properties are serialized as the empty string
Pass Valid fallback does not invalidate var()-reference [<length>, 10px]
Pass Valid fallback does not invalidate var()-reference [<length> | <color>, red]
Pass Valid fallback does not invalidate var()-reference [<length> | none, none]
Pass Invalid fallback doesn't invalidate var()-reference [<length>, red]
Pass Invalid fallback doesn't invalidate var()-reference [<length> | none, nolength]
Pass Invalid fallback doesn't invalidate var()-reference [<length>, var(--novar)]
Pass Empty universal custom property can be substituted with var()