Skip to content

[css-display] Inlinified layout-internal not well-defined #1582

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Loirooriol opened this issue Jul 5, 2017 · 3 comments
Closed

[css-display] Inlinified layout-internal not well-defined #1582

Loirooriol opened this issue Jul 5, 2017 · 3 comments

Comments

@Loirooriol
Copy link
Contributor

Now that #1390 removed the issue in the spec, the spec clearly says that e.g. an element with display: table-row that is inlinified should have an inline outer display type and a table-row inner display type. But this kind of box is not defined anywhere!

From #1390 it seems that inlinification should not affect layout-internal boxes.

@SelenIT
Copy link
Collaborator

SelenIT commented Jul 6, 2017

Doesn't anonymous box fixup occur in that case, so such box ends up being an inline table?

@Loirooriol
Copy link
Contributor Author

@SelenIT If it's not possible for a layout-internal box to be inlinified, the spec should say so. However, I think layout-internal boxes are inlinified, because inlinification happens before the creation of intermediary anonymous boxes, as explained in the note:

Note: There are two methods used to fix up box types when a box is mismatched to its context. One is transformation of the computed value of display, such as blockification and inlinification described here. The other, taking place during box tree construction (after computed values have been determined), is the creation of intermediary anonymous boxes, such as happens in tables, ruby, and flow layout.

Therefore, inlinification should have no effect on layout-internal boxes, and then they will generate anonymous boxes after inlinification.

@tabatkins tabatkins added the css-display-3 Current Work label Jul 11, 2017
@fantasai
Copy link
Collaborator

fantasai commented Jul 12, 2017

I'm not entirely sure what the issue is here, but I've clarified the spec by pointing out what @SelenIT describes in #1582 (comment)

Let me know if there's anything further to address.

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

No branches or pull requests

4 participants