Re: [csswg-drafts] [css-ruby] Size and position of empty ruby level containers (#4631)

The CSS Working Group just discussed `[css-ruby] Size and position of empty ruby level containers`, and agreed to the following:

* `RESOLVED: Empty ruby containers are sized as if they have empty things in them`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-ruby] Size and position of empty ruby level containers<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4631<br>
&lt;dael> florian: Spec doesn't say how to size if the containers are empty. Size to 0 is bad.<br>
&lt;dael> florian: If they're empty want to be sizes as if contain empty ruby base or ruby annotation<br>
&lt;dael> florian: Makes sense<br>
&lt;dael> astearns: Opinions?<br>
&lt;dael> astearns: Can you summarize?<br>
&lt;dael> florian: If a ruby-base container or ruby-annotation container is emty should be sized as if contain an empty ruby base or ruby annotation<br>
&lt;dael> florian: Empty thing container should be sized as if has empty of that thing.<br>
&lt;dael> AmeliaBR: If both base and annotation are empty we still want overall container to have vertical space?<br>
&lt;dael> florian: If you have ruby on an empty base you don't want ruby on base of whole thing just in the ruby thing. You want ruby to take the vertical space. If base container lakes a base you pretend it's emty and there<br>
&lt;dael> AmeliaBR: Like a strut that preserves line height for inline base and annotation?<br>
&lt;dael> florian: Yes<br>
&lt;dael> florian: To remind people there's a ruby box that contains a ruby base container that contains a ruby base and a ruby annotation container that contains a ruby annotation. When containers are empty they should not collapse to 0<br>
&lt;dael> astearns: Both empty containers and don't collapse so it's an empty space?<br>
&lt;dael> florian: Yes but width of 0<br>
&lt;dael> astearns: Prop: empty ruby containers are sizes as if they have empty things in them<br>
&lt;dael> nigel: Point on not observable.<br>
&lt;dael> fantasai: It is obervable if it's only constant of line. Will determine height of line<br>
&lt;fantasai> s/constant/content/<br>
&lt;dael> nigel: In inline direction...if you have ruby text that takes more inline space than ruby base if can spill out. Does an empty ruby base container effect flow of adjacent ruby text?<br>
&lt;dael> fantasai: You want to make sure thigns are paired correctly. Height of annotation and base are contained so stack at correct level. Don't want annotation to collapse to base<br>
&lt;dael> astearns: Purpose was to see if we should scope to if one of a pair is empty it's sized as if empty but if both are empty they collapse<br>
&lt;dael> fantasai: I don't think there's any prescedence to do that. Inline elements don't collapse to 0 when empty, they have height. Shoudl be consistent<br>
&lt;dael> astearns: nigel you okay with the side effects?<br>
&lt;dael> nigel: I was more concerned about width.<br>
&lt;dael> florian: I think this is about overhang?<br>
&lt;dael> nigel: Yeah<br>
&lt;dael> florian: 2 modes. One where you don't and one where UA does whatever it wants. Given it's not spec this doesn't interfere.<br>
&lt;dael> nigel: I could imagine that and empty thing with size 0 has position inline and that could overhang and effect adjacent things<br>
&lt;dael> fantasai: I think that's fine. THe empty thing holds its place. SHould be expected. If you don't want it to hold it's place it shouldn't be there<br>
&lt;dael> nigel: Feature. fair enough :)<br>
&lt;dael> fantasai: I think it's an edge case. I don't think there's anything to worry about in terms of edge cases<br>
&lt;dael> astearns: Good enough nigel?<br>
&lt;dael> nigel: yeah<br>
&lt;fantasai> s/edge/use/<br>
&lt;dael> astearns: Prop: Empty ruby containers are sized as if they have empty thigns in them<br>
&lt;dael> RESOLVED: Empty ruby containers are sized as if they have empty things in them<br>
</details>


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

Received on Wednesday, 15 April 2020 16:38:30 UTC