Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/w3c/csswg-drafts/issues/4935 below:

[css-ruby] define the height of the content area of ruby bases, ruby annotations · Issue #4935 · w3c/csswg-drafts · GitHub

The box model of ruby bases boxes and ruby annotations boxes is insufficiently defined. As far as I can tell, we have the following information:

• Base level contents of a ruby container box (presumably ruby base containers and ruby bases) are said to participate in the same inline formatting context that contains the ruby container itself. (in 2.2.1)
• The base level of a ruby structure is laid out on the line, aligned according to its vertical-align property exactly as if its ruby bases were a regular sequence of inline boxes (in 3)
• Ruby annotations within a level (within a single ruby container) are aligned to each other as if they were inline boxes participating in the same inline formatting context. (in 3)
• "In most respects, ruby boxes can be styled similar to inline boxes." (in 3)

This makes it reasonably clear that internal ruby boxes are similar in many ways to inline boxes, and specifically that the way the align vertically is identical to inline boxes (in the regular line for base level boxes, in a virtual line for annotations).

The spec does not actually define what the content area of ruby bases or ruby annotations are.

In the inline axis, this is already tracked at the in-spec issue 7.

In the block axis, due to the strong similarity with inline boxes, I suspect the intent is that it would be the same as if the ruby base / annotation had been an actual inline box, but the spec doesn't actually state so explicitly. Note that the content area of an inline box is itself currently undefined (see the second note in css-inline section 3.3.1), but making sure that these two are identical seems worth stating. Alternatively, if it is meant to be something else (possibly tailored to the predominantly CJK usage of ruby), then that should be stated instead.

This is actually more important here than with regular inlines, because unlike for regular inlines, this affects layout, not just painting: around this content area, comes the padding/border/margin, and around that comes the base containers and annotation containers, and annotation containers are then positioned adjacent to base containers. If we don't know the content area, we don't know where the ruby containers will be placed.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3