Do you want to know how the CSS WG works? Fantasai has written about:csswg, An Inside View of the CSS Working Group at W3C.
pageshould be a non-inherited property.
automeans look to the nearest non-
autoancestor and use that
pagevalue. Implementations that do inherit ‘page’ will be considered conformant to CSS3 Paged Media (since that is the currently-specified behavior), but not CSS4 Paged Media. We will add warning authors that the behavior of ‘page: auto’ would be unpredictable when used within an element with ‘page: somethingelse’.
Discussed overflow of multicolumn elements: whether new columns should be madd off to the side, or whether a new row of columns should be created as overflow below.
To create a layouts where a new set of columns are created below the first, we really would need a column-length property or somesuch and allow the height to be auto, otherwise the new columns will overflow the multicol element and overwrite later content.
Either way, multicolumn layout is not very usable on the screen because it’s designed for paginated media. So we discussed the idea of
overflow-style: paginate to create paginated layouts on the screen. (It would fall back to scrolling behavior on down-level clients.)
fantasai noted that the column width algorithm should define available width such that the UA can consider the available width on the page if that is less than the available width of the element.