Contact emails
mste...@chromium.orgExplainer
https://github.com/mstensho/column-wrapSpecification
https://drafts.csswg.org/css-multicol-2Summary
Add support for the `column-wrap` and `column-height` CSS properties, from multicol Level 2. https://drafts.csswg.org/css-multicol-2/#cwr https://drafts.csswg.org/css-multicol-2/#ch This allows for vertical column layout, or even 2D column layout. Columns can have an explicit constrained height, apart from being derived from the content-box height of the multicol container, and wrap to a new row of columns when all columns have been filled for one row, rather than creating overflowing columns in the inline direction.Blink component
Blink>Layout>MultiColWeb Feature ID
multi-columnMotivation
The primary motivation for introducing the new CSS properties `column-height` and `column-wrap` into the Multi-column Layout module is to gain greater control over the height of columns and enable the creation of content "rows" when the content overflows. Currently, the CSS Multi-column Layout module (multicol) is designed primarily for a single, continuous stream of content that flows down one column and then continues at the top of the next column, similar to a newspaper layout. This behavior is confined to a single "row" of columns.Initial public proposal
https://drafts.csswg.org/css-multicol-2/TAG review
https://github.com/w3ctag/design-reviews/issues/1073TAG review status
Issues addressedRisks
Debuggability
No information providedWill this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
YesYesFlag name on about://flags
MulticolColumnWrappingFinch feature name
MulticolColumnWrappingRollout plan
Will ship enabled for all usersRequires code in //chrome?
FalseTracking bug
https://issues.chromium.org/issues/403183884Estimated milestones
| Shipping on desktop | 144 |
| Shipping on Android | 144 |
| Shipping on WebView | 144 |
Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
No information providedLink to entry on the Chrome Platform Status
https://chromestatus.com/feature/5176206485618688?gate=5179956763820032Links to previous Intent discussions
Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKWZFm6Fq87884oWbi%2BMT0XDipMWWxm0G%2Bk6M1s%3Dp8fmgyqL5w%40mail.gmail.com