8000
Skip to content
/ csswg-drafts Public

[css-display][css-ruby] Does inlinification really need recursion? #1341

Closed
Closed
[css-display][css-ruby] Does inlinification really need recursion?#1341
Labels
Closed Accepted by CSSWG ResolutionChanges backed by a CSSWG resolution.Tracked in DoCcss-display-3Current Workcss-ruby-1Current Work

Description

@Loirooriol
Loirooriol
opened on May 9, 2017

CSS Display defines inlinification as such:

inlinification [...] sets the box’s outer display type, if it is not none or contents, to [...] inline [...]

If a box with a flow inner display type is inlinified, it recursively inlinifies all of its in-flow children, so that no block-level descendants break up the inline formatting context in which it participates.

I think it makes more sense to transform the flow inner display type into flow-root. That is, transform block to inline-block. Then the box will be an atomic inline, and thus block-level descendants won't break up the inline formatting context. Recursive inlinification is not needed.

This seems what Firefox does for ruby. Chrome and Edge don't inlinify at all. https://jsfiddle.net/d1o5k7Ly/1/

It's worth noting that CSS Ruby says "directly contained"

Inlinize block-level boxes: Any in-flow block-level boxes directly contained by a ruby container, ruby base container, ruby annotation container, ruby base box, or ruby annotation box are forced to be inline-level boxes, and their display value computed accordingly.

By the way, are inlinization and inlinification synonyms?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Closed Accepted by CSSWG ResolutionChanges backed by a CSSWG resolution.Tracked in DoCcss-display-3Current Workcss-ruby-1Current Work

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
    0