Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
longhands: ["column-width", "column-count", "column-height", "column-wrap"],
I think `transition-property:columns` will start transitioning `column-height` and `column-wrap` regardless of the runtime flag?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
longhands: ["column-width", "column-count", "column-height", "column-wrap"],
I think `transition-property:columns` will start transitioning `column-height` and `column-wrap` regardless of the runtime flag?
I was concerned about this change, too. I was wondering how StylePropertySerializer::CommonShorthandChecks() would work when the feature is disabled. But `longhand_count` is 2 when the feature is disabled, and 4 if it's enabled. Since `column-height` and `column-wrap` only exist when the feature is enabled, there seems to be a fairy that takes care of this for us?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Code-Review | +1 |
longhands: ["column-width", "column-count", "column-height", "column-wrap"],
Morten StenshorneI think `transition-property:columns` will start transitioning `column-height` and `column-wrap` regardless of the runtime flag?
I was concerned about this change, too. I was wondering how StylePropertySerializer::CommonShorthandChecks() would work when the feature is disabled. But `longhand_count` is 2 when the feature is disabled, and 4 if it's enabled. Since `column-height` and `column-wrap` only exist when the feature is enabled, there seems to be a fairy that takes care of this for us?
I was concerned about this change, too. I was wondering how StylePropertySerializer::CommonShorthandChecks() would work when the feature is disabled. But `longhand_count` is 2 when the feature is disabled, and 4 if it's enabled. Since `column-height` and `column-wrap` only exist when the feature is enabled, there seems to be a fairy that takes care of this for us?
Ah, I missed that these are both covered by the runtime flag. Then they're filtered by the python scripts.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Add `column-height` to `columns` shorthand. Reset `column-wrap`.
Add `column-height` to the `columns` shorthand, as resolved here:
https://github.com/w3c/csswg-drafts/issues/12050#issuecomment-3160860557
The new syntax is: `[ <'column-width'> || <'column-count'> ] [ / <'column-height'> ]?`.
Additionally the `columns` shorthand now resets the `column-wrap`
property to its initial value.
The new serialization code for `columns` also strips extraneous `auto`
keywords, so that e.g. `columns:auto` gets serialized as `columns:auto`,
not `columns:auto auto`, so that round-tripping no longer fails in
CSSParserImplTest.AllPropertiesCanParseImportant. This fix also affects
other tests, so that their expectations had to be updated.
Furthermore, since new longhands are added to the `columns` shorthand,
specifying only `column-count` and `column-width` now will result in
an empty string from getPropertyValue("columns"), since two longhands
are missing. Tests had to be updated because of this as well.
All behind runtime flag MulticolColumnWrapping.
Generated with gemini-cli assistance #ai-assisted (except for tests -
they are handwritten)
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
The WPT PR for this CL has been merged upstream! https://github.com/web-platform-tests/wpt/pull/54423
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |