-
Notifications
You must be signed in to change notification settings - Fork 815
[css-display][css-ruby] Inlinification Considerations #1390
Copy link
Copy link
Closed
Labels
Closed Accepted as Obvious BugfixFixed an obvious error with the obvious solution.Fixed an obvious error with the obvious solution.Commenter SatisfiedCommenter has indicated satisfaction with the resolution / edits.Commenter has indicated satisfaction with the resolution / edits.Tracked in DoCcss-display-3Current WorkCurrent Workcss-ruby-1Current WorkCurrent Worki18n-trackerGroup bringing to attention of Internationalization, or tracked by i18n but not needing response.Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
Description
Activity
Metadata
Metadata
Assignees
Labels
Closed Accepted as Obvious BugfixFixed an obvious error with the obvious solution.Fixed an obvious error with the obvious solution.Commenter SatisfiedCommenter has indicated satisfaction with the resolution / edits.Commenter has indicated satisfaction with the resolution / edits.Tracked in DoCcss-display-3Current WorkCurrent Workcss-ruby-1Current WorkCurrent Worki18n-trackerGroup bringing to attention of Internationalization, or tracked by i18n but not needing response.Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
Inlinification (such as what happens to the block-level contents of a run-in or ruby annotation) currently doesn't affect the display of layout-internal types like
table-row: for these boxes no computed valuedisplayalteration happens, and anonymous box fixup will wrap them accordingly. Blockification instead converts the display value toblock(so no anonymous box fixup happens, and also any further structure inside it is disrupted by the conversion toblock). Is there a reason to do one vs the other here?