I suspect the latter two failures are bogus; the test seems to be expecting `inline-size` to be serialized at the start, but the spec doesn't make any such guarantee. In fact, the spec lists that keyword as the last thing in its grammar: ``` New values: layout || style || paint || [ size | inline-size ] ``` https://drafts.csswg.org/css-contain-3/#contain-property ...though really the order doesn't matter since `||` means "can occur in any order".
Bug 1744309 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
~~I suspect the latter two failures are bogus; the test seems to be expecting `inline-size` to be serialized at the start, but the spec doesn't make any such guarantee.~~ In fact, the spec lists that keyword as the last thing in its grammar: ``` New values: layout || style || paint || [ size | inline-size ] ``` https://drafts.csswg.org/css-contain-3/#contain-property ...though really the order doesn't matter since `||` means "can occur in any order". EDIT: it looks like the order does actually matter for serialization purposes per https://drafts.csswg.org/cssom/#serialize-a-css-value (see bullet point about canonical order and `||` there). css-contain-1 does have `size` at the start, and css-contain-3 changed that when adding `inline-size`, possibly by accident. I filed https://github.com/w3c/csswg-drafts/issues/8600 to clear that up.
~~I suspect the latter two failures are bogus; the test seems to be expecting `inline-size` to be serialized at the start, but the spec doesn't make any such guarantee.~~ In fact, the spec lists that keyword as the last thing in its grammar: ``` New values: layout || style || paint || [ size | inline-size ] ``` https://drafts.csswg.org/css-contain-3/#contain-property ~...though really the order doesn't matter since `||` means "can occur in any order".~ EDIT: it looks like the order does actually matter for serialization purposes per https://drafts.csswg.org/cssom/#serialize-a-css-value (see bullet point about canonical order and `||` there). css-contain-1 does have `size` at the start, and css-contain-3 changed that when adding `inline-size`, possibly by accident. I filed https://github.com/w3c/csswg-drafts/issues/8600 to clear that up.