- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Jan 2023 18:03:42 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-text-4] Re-use justify-content instead of text-group align?`. <details><summary>The full IRC log of that discussion</summary> <bramus> jensimmons: I can describe<br> <bramus> jensimmons: text-wrap is a property and balance is value for it<br> <bramus> jensimmons: it enables to do balanced text for text that spans multiple lines<br> <fantasai> -> https://www.w3.org/TR/css-text-4/#text-group-align-property<br> <bramus> jensimmons: text-group in text level 4 is the new property to accomplish that use case<br> <bramus> jensimmons: do we need this new property or should we use justify-content?<br> <fantasai> -> https://www.w3.org/TR/css-align-3/#align-justify-content<br> <bramus> ntim: makes sense to reuse justify-content<br> <bramus> ntim: [missed]<br> <bramus> iank_: justifty-content will start new formatting context, right?<br> <bramus> fantasai: yes<br> <bramus> iank_: so that is one relative difference between the two<br> <bramus> fantasai: we could define it to not do that<br> <bramus> iank_: would align-content be harmonized?<br> <bramus> fantasai: that one needs it<br> <bramus> fantasai: in terms of inline-axis one thing that gets weird when we don}t create formatting context: what happens when we have floats?<br> <bramus> fantasai: (gives example)<br> <bramus> florian: I think it’s good to create the formatting context<br> <bramus> florian: then floats dont do strange things<br> <fantasai> s/(gives example)/for floats inside the box it's straightforward, but if floats are intruding from the parent... it gets weird/<br> <bramus> astearns: questoins about formatting contexts and floats are questions for either new property or the existing property<br> <bramus> iank_: float question falls into two sub questions<br> <bramus> iank_: would make easier if floats dont intrude from outside<br> <bramus> iank_: how floats withing that ifc interacts is another question.<br> <bramus> florian: i think alan is right that that concern applies to both properties<br> <bramus> iank_: I want to point out formatting context difference.<br> <bramus> fantasai: I thiknk what florian is trying to say: either way since neithe rpropert is implemented right now, we can decide what to do. question applie sto both properties<br> <bramus> iank_: slight forward compat risk with reusing justify-content<br> <bramus> fantasai: less concerned about that<br> <bramus> fantasai: currently when you have a bunch of line boxes they [missed] in container. we have to tell those boxes to be shortened<br> <florian> s/ they [missed] in/ they fill in/<br> <bramus> fantasai: and then there is this fun interaction with line boxes. say i have a div and center it. in order for it to be centered we have to shorten line boxes. that is striaghtfowrad if boxes are directly contained by div. what if that div contains other divs?<br> <bramus> fantasai: do we some kind of propagation? do we inherit? do we not affect any of the child divs? etc.<br> <bramus> fantasai: with justify-content there is more of a consensus that you lay out all children as a unit<br> <iank_> justify-content creating a new formatting-context is a relatively large compat risk IMO<br> <bramus> fantasai: [missed]<br> <bramus> fantasai: so it will not have any effect of centering the text.<br> <bramus> iank_: if that list is shortening all the line boxes that [missed]<br> <bramus> astearns: seems like issue that is going to come up for either version of the property<br> <bramus> astearns: can we resolve on using justify-content or not?<br> <bramus> iank_: compat risk is making justify-content establish a new formatting context<br> <bramus> iank_: things suddenly become fc when they were not previously<br> <bramus> florian: assuming people already use this property<br> <bramus> iank_: exactly<br> <fantasai> specifically to blocks that are not already BFCs<br> <bramus> florian: can we have a use counter to check?<br> <bramus> iank_: i think apple folks are more interested in shipping<br> <bramus> astearns: should prioritize whether we should create new fc or not and use that info to decide if we reuse property or go with proposed thing<br> <bramus> florian: yes [missed]<br> <bramus> astearns: we are at time<br> <bramus> astearns: lets take back to github<br> <bramus> astearns: most likely need more discussion on compat issue<br> <florian> s/yes [missed]/yes, though we might still be able to go with justify-content even if we want a fc depending on the compat situation/<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5703#issuecomment-1387491602 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 January 2023 18:03:43 UTC