Re: [csswg-drafts] [css-writing-modes] Should max-height also limit orthogonal flows?

The Working Group just discussed `[css-writing-modes] Should max-height also limit orthogonal flows?`, and agreed to the following resolutions:

* `RESOLVED: Accept proposal in issue #2239`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-writing-modes] Should max-height also limit orthogonal flows?<br>
&lt;fantasai> lajava, rego: If we can't solve before subgrid needs to ship, we can drop to the next level :)<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2239<br>
&lt;rego> :-)<br>
&lt;lajava> fantasai: sounds good<br>
&lt;dael> fantasai: We use the...if you have orthogonal flow we need to come up with a height contraint on vertical text so there's a line length.<br>
&lt;dael> fantasai: By default we use a combo of containing block if it's defined or nearest scrollport or initial containg block.<br>
&lt;dael> fantasai: Scrollport we only use if its fixed height.<br>
&lt;dael> fantasai: For contianing block we forgot to look at max height.<br>
&lt;dael> fantasai: Proposal is to modify spec to look at max height when there's and auto and a max.<br>
&lt;dael> fantasai: There is one impl already.<br>
&lt;dael> florian: We have 1 1/2 impl. Blink and Webkit do it.<br>
&lt;dael> Rossen_: From impl PoV it sounds reasonable.<br>
&lt;dael> Rossen_: We might already support this. It's been a while since I played with orthogonal flows. But it makes perfect sense.<br>
&lt;dael> Rossen_: Other thoughts, ideas, obj on having max-height be a constraint?<br>
&lt;dael> florian: I'm in favor we should look in all cases, not some.<br>
&lt;dael> fantasai: Agree.<br>
&lt;rego> +1<br>
&lt;dael> Rossen_: Would be good when we spec lang to word it such that the used content box height will be defined rather then auto. I'm saying this b/c we don't want to have to come back and say min-height also needs to be looked at in case it's bigger. Would be better to define it as defined not auto.<br>
&lt;liam> presnet+<br>
&lt;dael> fantasai: Yeah. We need to make sure we word for all cases. We can't use used height because if it's auto it depends on this ortogonal flows.<br>
&lt;dael> Rossen_: Agree.<br>
&lt;dael> Rossen_: Something like content box height would be defined. There's a combo of max an dmin height to make a limit.<br>
&lt;dael> fantasai: Sounds good.<br>
&lt;dael> Rossen_: I jsut don't want to ignore min height in this or have it sound like only max applies.<br>
&lt;dael> fantasai: Good point.<br>
&lt;dael> florian: Rossen_ to make sure I follow you say if min ehight is large it could come into account but smaller doesn't matter.<br>
&lt;dael> Rossen_: If there's something that will define a limit, such as max or min height. Min height only pushes the limit if it exists. Provided a limit exists and you have to look at min height it's used. I don't want us to forget about min height which is pushing the limit.<br>
&lt;dael> Rossen_: I didn't know how to clearly define it so I said used height but that's weak.<br>
&lt;dael> florian: Your point should be equalliy valid for containing block as scope. But yeah, I agree.<br>
&lt;fantasai> sgtm, I'll make the edits and Florian will review ;)<br>
&lt;dael> Rossen_: I think we have enough in the discussion that will go into the minutes. Anything else to add?<br>
&lt;dael> florian: Good to resolve<br>
&lt;dael> RESOLVED: Accept proposal in issue #2239<br>
</details>


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

Received on Wednesday, 31 January 2018 17:25:40 UTC