mirror of
https://github.com/LadybirdBrowser/ladybird
synced 2026-04-26 01:35:08 +02:00
9fe8445946
Previously, for `foo < 30px` ranges, we'd flip them and store them as `30px > foo` instead. That worked fine, but means the serialization is wrong. So instead, keep them in their original form. I experimented with giving Range two optional sub-structs instead of 4 optional members, thinking it would be smaller - but it's actually larger, because the two Optional<Comparison>s fit snugly together. So, the slightly-goofy all-Optionals remains. This gets us 2 WPT passes that I'm aware of.
7 lines
198 B
Plaintext
7 lines
198 B
Plaintext
Harness status: OK
|
|
|
|
Found 2 tests
|
|
|
|
2 Pass
|
|
Pass Empty CSSNestedDeclarations do not affect outer serialization
|
|
Pass Empty CSSNestedDeclarations do not affect outer serialization (nested grouping rule) |