Skip to content

[css-break] Is an inline-block monolithic or may-be? #1111

Closed

Description

@kojiishi

Recently I happened to be in a discussion whether the 4.1. Possible Break Points section in CSS Fragmentation Module defines an inline-block must be monolithic or may be monolithic. I could read both ways, clarification is appreciated.

There are two paragraphs that may be read differently.

First it says:

Some content is not fragmentable, for example ... or a single line of text content. Such content is considered monolithic

IIUC this paragraph doesn't define inline-block yet since inline-block is not text content, but I could read it differently, considering inline-block is abstracted as an object replacement character.

Then it says:

Since line boxes contain no possible break points, inline-block and inline-table boxes (and other inline-level display types that establish a new formatting context) may also be considered monolithic.

The last part clearly defines inline-block may be monolithic. However, this paragraph also says "line boxes contain no possible break points", I could read this as "inline-block appearing in a line box must not be broken." An inline-block cannot live outside of a line box, so this paragraph maybe self contradicting depends on how you read.

@fantasai could you help to clarify?

Note, from our brief testing, in case this helps:

  • Gecko does not break an inline-block.
  • Edge/Trident can break an inline-block, normally between line boxes in the inline-block.
  • WebKit/Blink can break an inline-block at arbitrary points.

Activity

  1. changed the title [-][css-break] Is an inline-block monolithic or not?[/-] [+][css-break] Is an inline-block monolithic or may-be?[/+] on Mar 16, 2017
  2. tabatkins commented on Mar 17, 2017

    @tabatkins
    Member

    I'm pretty sure this is just clumsy 2119 usage. It should be s/may also be/are/.

  3. fantasai commented on Mar 20, 2017

    @fantasai
    Collaborator

    I think we made this a MAY case so that an implementation could fragment an inline block, if it wanted to--didn't want to forbid it, since that can be a better result than what the spec requirs. The alternatives are to clip the line box it's in or to graphically slice said line box and all its contents.

  4. fantasai commented on Aug 20, 2018

    @fantasai
    Collaborator

    I added some text to clarify this case. @kojiishi can you let me know whether the intention is clear enough now?

  5. kojiishi commented on Sep 12, 2018

    @kojiishi
    ContributorAuthor

    Looks great, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions