Re: [csswg-drafts] [css-ruby] define the height of the content area of ruby containers (#4936)

The CSS Working Group just discussed `[css-ruby] define the height of the content area of ruby containers`, and agreed to the following:

* `RESOLVED: height of the content area of ruby container box is calculated the same as inline boxes`

<details><summary>The full IRC log of that discussion</summary>
&lt;Rossen_> Topic: [css-ruby] define the height of the content area of ruby containers<br>
&lt;Rossen_> github: https://github.com/w3c/csswg-drafts/issues/4936<br>
&lt;TabAtkins> florian: Around ruby bases and annos, each have base containers and anno containers, and around all of that there's a ruby container. We're talking about that one.<br>
&lt;TabAtkins> florian: Its content height isn't defined either<br>
&lt;TabAtkins> florian: A bit subtle, e haven't walked about the various boxes yet. But you can put a bakground on the ruby container and see it's height<br>
&lt;TabAtkins> florian: In all impls, the answer here is the same as for previous question. They're treated as inlines; background goes behind the base layer and that's it.<br>
&lt;TabAtkins> florian: Since we'll see in othe rissues that we don't need that box to grow, I'm inclined to match impls.<br>
&lt;fantasai> sgtm<br>
&lt;TabAtkins> AmeliaBR: What does that mean?<br>
&lt;tantek> There's a lot of questions about &amp; undefined aspects about Ruby layout despite there being multiple implementations, perhaps we need tests to see what existing implementations do and whether they've converged or not? Instead of a priori / aspirationally answering the questions of what "should" happen.<br>
&lt;TabAtkins> fantasai: If a background is on &lt;ruby> itself, it'st he same as a background on a &lt;span> around the ruby<br>
&lt;TabAtkins> AmeliaBR: Is the anno included?<br>
&lt;TabAtkins> fantasai: No<br>
&lt;myles> AmeliaBR++<br>
&lt;TabAtkins> AmeliaBR: ARe there use-cases for having it cover the anno?<br>
&lt;TabAtkins> fantasai: Dunno. Backgrounds on ruby in general doesn't appear existent.<br>
&lt;TabAtkins> fantasai: If you don't care about linebreaking you can get that behavior by setting it to inline-block anyway<br>
&lt;faceless2_> Styling the &lt;rt> with &lt;rt style="background-color:inherit"> works to give the annotation the same color<br>
&lt;myles> faceless2_: it's not the same, though. the RT and the RB can have different widths<br>
&lt;TabAtkins> AmeliaBR: So if you actually want a background that highlights the base and the anno, we're saying that's not possible without giving up fragmentation right now.<br>
&lt;TabAtkins> florian: You can put a background on both bases and annos.<br>
&lt;fremy> ^ exactly what I was gonna way<br>
&lt;TabAtkins> florian: They're contiguous.<br>
&lt;TabAtkins> AmeliaBR: They're not the same length, are they?<br>
&lt;TabAtkins> florian: They should be, yes. A little underspecified.<br>
&lt;TabAtkins> fantasai: Given that the ruby box doesn't really affect layout, I think we should resolve on this; we can reconsider it if anyone asks for it<br>
&lt;TabAtkins> Rossen_: Objections?<br>
&lt;florian> RESOLVED: height of the content area of ruby container box is calculated the same as 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/4936#issuecomment-622125781 using your GitHub account

Received on Thursday, 30 April 2020 21:32:19 UTC