-
Notifications
You must be signed in to change notification settings - Fork 719
[css-multicol] specification should define interaction between 'column-span' and 'column-fill' #1075
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think requiring the balance-all behavior on all preceding pages is an unintended side effect of the imprecise wording you mentioned, and that "balanced across all columns before the element appears." should be scoped to the current fragmentainer. |
How about honoring |
Removing agenda+ until #1072 is resolved |
The Working Group just discussed The full IRC log of that discussion |
…ately preceding the spanner #1075
…ately preceding the spanner w3c#1075
The multicol spec doesn't define the interaction between 'column-fill' and elements that have 'column-span'. The definition of column-span says:
I think it's reasonably clear that in a non-paged context, this means that
column-fill
is only honored in the part of the multicol after the lastcolumn-span: all
element inside it. However, it's less clear what happens in paged media. Reading the text quoted above literally, the spec currently says thatcolumn-fill: balance-all
behavior (rather thanbalance
, which is the initial value) is required on any pages of a multicolumn element where a later page has a column-spanning element.This should actually be defined in a somewhat formal manner. The current spec appears to be more of a use cases document than a specification on this topic.
/cc @neerjapancholi
The text was updated successfully, but these errors were encountered: