Re: [csswg-drafts] [css-ruby] define the height of the content area of ruby bases, ruby annotations (#4935)

The CSS Working Group just discussed `height of content area of bases and annotations`, and agreed to the following:

* `RESOLVED: The height of the content are of ruby boxes and annos is calculated the same as for inline boxes`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> Topic: height of content area of bases and annotations<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/4935<br>
&lt;TabAtkins> florian: A number of palces in the ruby spec that vaguely, implicitly, alludes to bases and annos being *quite similar* to inline boxes<br>
&lt;TabAtkins> florian: But they're not inline, they're ruby, they're just very similar.<br>
&lt;TabAtkins> florian: But the precise wyay they're similar isn't specified<br>
&lt;TabAtkins> florian: One way not specified is how to calculate height of the ocntent area<br>
&lt;TabAtkins> florian: For inlines we're working ons pecifying that<br>
&lt;TabAtkins> florian: Like elika said, presuambly once they work for inline, they should work for rubys<br>
&lt;TabAtkins> florian: But they should. We've been implying that, but havne't said so.<br>
&lt;TabAtkins> dbaron: I feel more strongly that ruby bases shoudl behave like inlines, than that annos should<br>
&lt;TabAtkins> dbaron: bases are basically just partof the line, and annos are outside of them<br>
&lt;xidorn> q+<br>
&lt;AmeliaBR> q+<br>
&lt;TabAtkins> dbaron: So making bases different from inlines is bad, because it means when you have ruby you rinline formatting becomes different in unexpected ways<br>
&lt;TabAtkins> dbaron: While annos might need some more differences<br>
&lt;Rossen_> +1 to dbaron<br>
&lt;TabAtkins> florian: We do have some reasons to have bases differ from inlines; we don't have reasons for annos to differ from bases.<br>
&lt;TabAtkins> florian: If we find reasons later, we can differentiate them, while keeping the same for now<br>
&lt;TabAtkins> Rossen_: When ruby-overhang comes into play we might have some diffs, but otherwise agree<br>
&lt;TabAtkins> xidorn: I think annos should behave like inlines a swell; anno has a container and it basically just lines up inside the container like an inline<br>
&lt;Rossen_> ack xidorn<br>
&lt;Rossen_> ack AmeliaBR<br>
&lt;TabAtkins> AmeliaBR: I agree we should reuse as much inline model as possible, but let's not oversimplify<br>
&lt;TabAtkins> AmeliaBR: Like, how line-height is integrated intot he inline box will be more complex than just looking at the base...<br>
&lt;TabAtkins> florian: Actually, that's a spearate issue we'll get to<br>
&lt;TabAtkins> florian: So proposed resolution is to define that th eheight of the content area of ruby bases and annos is calculated the same as inline boxes<br>
&lt;TabAtkins> AmeliaBR: Within what block context?<br>
&lt;TabAtkins> AmeliaBR: An isolated block context created by the ruby container? Or same as if inlines were in the parent block context?<br>
&lt;TabAtkins> fantasai: Why does that matter<br>
&lt;TabAtkins> ?<br>
&lt;TabAtkins> AmeliaBR: Not sure<br>
&lt;TabAtkins> fantasai: We're just talking about heights. Bases are considered to be part of the line: particpiate in line-height, justification, etc just as if they were inlines. They just get some extra space for annos, otherwise they're just normal text.<br>
&lt;TabAtkins> AmeliaBR: If it all adds up to the same, that's fine<br>
&lt;TabAtkins> RESOLVED: The height of the content are of ruby boxes and annos is calculated the same as for inline boxes<br>
</details>


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

Received on Thursday, 30 April 2020 21:25:47 UTC