-
Notifications
You must be signed in to change notification settings - Fork 719
[css-multicol] Multi-col, spanner margin collapsing, and formatting contexts #2582
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
Labels
Comments
The Working Group just discussed
The full IRC log of that discussion |
|
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this issue
Sep 10, 2019
…is enabled. r=dbaron Based on CSS working group's resolution in w3c/csswg-drafts#2582 (comment), column-boxes are BFC. Add NS_BLOCK_FORMATTING_CONTEXT_STATE_BITS to -moz-column-content, but only for the new multicol layout. Differential Revision: https://phabricator.services.mozilla.com/D43904 --HG-- extra : moz-landing-system : lando
xeonchen
pushed a commit
to xeonchen/gecko
that referenced
this issue
Sep 10, 2019
…is enabled. r=dbaron Based on CSS working group's resolution in w3c/csswg-drafts#2582 (comment), column-boxes are BFC. Add NS_BLOCK_FORMATTING_CONTEXT_STATE_BITS to -moz-column-content, but only for the new multicol layout. Differential Revision: https://phabricator.services.mozilla.com/D43904
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-comments-removed
that referenced
this issue
Oct 4, 2019
…is enabled. r=dbaron Based on CSS working group's resolution in w3c/csswg-drafts#2582 (comment), column-boxes are BFC. Add NS_BLOCK_FORMATTING_CONTEXT_STATE_BITS to -moz-column-content, but only for the new multicol layout. Differential Revision: https://phabricator.services.mozilla.com/D43904 UltraBlame original commit: 1e447195b68c5012751e90497ba97a6421e3669e
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified-and-comments-removed
that referenced
this issue
Oct 4, 2019
…is enabled. r=dbaron Based on CSS working group's resolution in w3c/csswg-drafts#2582 (comment), column-boxes are BFC. Add NS_BLOCK_FORMATTING_CONTEXT_STATE_BITS to -moz-column-content, but only for the new multicol layout. Differential Revision: https://phabricator.services.mozilla.com/D43904 UltraBlame original commit: 1e447195b68c5012751e90497ba97a6421e3669e
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified
that referenced
this issue
Oct 4, 2019
…is enabled. r=dbaron Based on CSS working group's resolution in w3c/csswg-drafts#2582 (comment), column-boxes are BFC. Add NS_BLOCK_FORMATTING_CONTEXT_STATE_BITS to -moz-column-content, but only for the new multicol layout. Differential Revision: https://phabricator.services.mozilla.com/D43904 UltraBlame original commit: 1e447195b68c5012751e90497ba97a6421e3669e
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Example 25 in multicol contains the following sentence:
This seems reasonable, and I believe we discussed this and resolved in favor of it years ago, but I do not think it is fully supported by normative text. It is not contradicted by normative text either, but given that the multicol container is not a normal block formatting context, the behavior does not just fall out, and needs to be specified.
Arguably, it may fall out of this sentence, in section 2:
but that sentence itself seems strange to me, since a BFC wouldn't know what to do with column boxes, spanners, and the like. The content of the multicol goes into a BFC, but that it doesn't seem to me that the BFC is the multicol container itself. Shouldn't we rather say that:
By the way, I am not sure if that should be a single column box establishing a single BFC, with each column being a fragment of that single box, or if each column is by itself a box which establishes a BFC. The former sounds more intuitive to me, the later seems a more similar to how we describe line boxes.
Alternatively:
Finally, we also probably need:
The text was updated successfully, but these errors were encountered: