Re: [csswg-drafts] [css-writing-modes-4] Allow sideways-x and vertical-x to share a block formatting context? (#10714)

The CSS Working Group just discussed `[css-writing-modes-4] Allow sideways-x and vertical-x to share a block formatting context?`, and agreed to the following:

* `RESOLVED: Allow consistent sideways-* and vertical-* writing modes to share a BFC`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> fantasai: WM3 said if you have a different writing mode, you form a different bfc<br>
&lt;TabAtkins> fantasai: made sense then, each wm went in a different block-flow direction<br>
&lt;TabAtkins> fantasai: but in WM4 we introduced the sideways variants, which differ from vertical only in line orientation<br>
&lt;TabAtkins> fantasai: so switching between thos edoesn't change block flow direciton, probably doesn't need a new bfc<br>
&lt;TabAtkins> fantasai: so does it make sense to allow them to share a bfc?<br>
&lt;TabAtkins> fantasai: in terms of use-cases, say an english block quote inside of vertical japanese<br>
&lt;TabAtkins> fantasai: and you formatted that with sideways-*<br>
&lt;TabAtkins> astearns: so firefox ships the sideways keywords. does it establish a new bfc there?<br>
&lt;TabAtkins> fantasai: haven't checked, but also don't think we're under compat pressure here<br>
&lt;TabAtkins> jfkthame: i think it does establish a bfc, but think we could change that without too much difficulty<br>
&lt;TabAtkins> astearns: and ???'s comment is that we shoudln't change the spec unless there's a good author use-case<br>
&lt;astearns> s/???/Kent/<br>
&lt;TabAtkins> fantasai: i think if you do mix these two... the cases where there is a behavior difference are rare<br>
&lt;TabAtkins> fantasai: but if you did end up in such a sitaution, you'd want them to be in the same bfc<br>
&lt;fantasai> TabAtkins: obvious example is a float. If you started in Japanese, and then switched to sideways English, and float intruded into the English paragraph<br>
&lt;TabAtkins> astearns: so proposal is to change the spec to not require a new bfc between sideways-* and vertical-* WM changes<br>
&lt;TabAtkins> astearns: and we'll see if it's web compatible<br>
&lt;oriol> The author can always force a bfc manually if desired<br>
&lt;TabAtkins> fantasai: yes. i suspect it is since firefox is the only one shipping sideways rn<br>
&lt;TabAtkins> astearns: comments or objections?<br>
&lt;TabAtkins> RESOLVED: Allow consistent sideways-* and vertical-* writing modes to share a BFC<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10714#issuecomment-2518161715 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 4 December 2024 18:00:19 UTC