You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[css-break] Is an inline-block monolithic or may-be? #1111
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.
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.
Activity
[-][css-break] Is an inline-block monolithic or not?[/-][+][css-break] Is an inline-block monolithic or may-be?[/+]tabatkins commentedon Mar 17, 2017
I'm pretty sure this is just clumsy 2119 usage. It should be
s/may also be/are/.[LayoutNG] Implement atomic inlines for LayoutNGInline
fantasai commentedon Mar 20, 2017
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.
fantasai commentedon Aug 20, 2018
I added some text to clarify this case. @kojiishi can you let me know whether the intention is clear enough now?
[css-break-3] Clarify the case where the UA may treat inline-level bo…
kojiishi commentedon Sep 12, 2018
Looks great, thank you.