Skip to content
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

[css-display] Position of 'list-item' when serializing <display-listitem> #1621

Closed
Loirooriol opened this issue Jul 20, 2017 · 2 comments
Closed
Labels
Commenter Satisfied Commenter has indicated satisfaction with the resolution / edits. css-display-3 Current Work Tracked in DoC

Comments

@Loirooriol
Copy link
Contributor

The summary table in CSS Display says that list-item inline flow serializes to inline list-item.

However, the syntax is

<display-listitem> = list-item && <display-outside>? && [ flow | flow-root ]? ;

Then, according to the "shortest serialization" principle (which is going to be reintroduced in #1564), it should serialize to list-item inline:

Where multiple CSS component values can appear in any order without changing the meaning of the value (typically represented by a double bar || in the value syntax), use the order as given in the syntax.

Therefore, I think either the summary table should say list-item inline or the syntax of <display-listitem> should move the list-item keyword to the end.

@Loirooriol
Copy link
Contributor Author

@tabatkins Then you should also reorder list-item block flow and list-item inline flow entries in the "Full display" column of the summary table.

@fantasai
Copy link
Collaborator

@Loirooriol Done, thanks.

@fantasai fantasai added the Commenter Satisfied Commenter has indicated satisfaction with the resolution / edits. label Mar 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Commenter Satisfied Commenter has indicated satisfaction with the resolution / edits. css-display-3 Current Work Tracked in DoC
Projects
None yet
Development

No branches or pull requests

3 participants