Skip to content

[css-display] How are 'list-item run-in flow' and 'list-item block flow-root' serialized? #1493

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 Jun 2, 2017 · 2 comments

Comments

@Loirooriol
Copy link
Contributor

Some display values with list-item keyword can be shortened to a single keyword:

  • list-item block flow can be shortened to list-item
  • list-item inline flow can be shortened to inline-list-item

Some display values with list-item keyword require all three keywords:

  • list-item run-in flow-root
  • list-item inline flow-root

The other display values with list-item keyword can be shortened to two keywords:

  • list-item run-in flow can be shortened to list-item run-in
  • list-item block flow-root can be shortened to list-item flow-root

This question is about the last case. Do they serialize to the two-keyword shortened form, or do they stay in the full form?

CSS Display says

Following the precedence rules of “most backwards-compatible, then shortest”, serialization of equivalent display values uses the “Short display” column.

So it seems short forms are preferred, but these combinations do not appear in the summary table!

@tabatkins tabatkins added the css-display-3 Current Work label Jun 5, 2017
@tabatkins
Copy link
Member

The table is an informative guide to help authors, not a normative and complete mapping table. The note at the end is just that—a note, reminding you that things get serialized to their shortest form, and that the table contains many of those. But the "3 keywords that can be written as 2" is already covered by that general principle.

(However, see #1564.)

@fantasai
Copy link
Collaborator

(Marking Wontfix because we won't fix the informative table; but the serialization should be clearly defined in CSSOM, and #1564 is open against it to ensure it contains the general rules for serialization once again.)

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

3 participants