Re: [csswg-drafts] [css-lists] canonical property order of list-style.

I think this is unrelated to the syntax change, and it's a case of usage of `||` when multiple items can accept the same value.

In Gecko, what we do is, during parsing value of `list-style` shorthand, we record number of `none` we see, and try parsing only non-`none` parts with parsing function of longhands in the (proposed) canonical order.  After that, we check whether number of `none` is reasonable, and decide which longhands they should fill.

It seems to me this is the only reasonable behavior for handling `||` in this case. This behavior have been existing in Gecko even longer than the canonical order change, and the canonical order change doesn't affect the behavior on this for us.

It's probably not very common that a shorthand has multiple longhands which accept the same value outside the case of `<custom-ident>`, and grepping our code, I only find two: one is `list-style` which can accept `none` for two longhands, another is `columns` which can accept `auto` for two. In Gecko, we handle them in the same manner described above.

-- 
GitHub Notification of comment by upsuper
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2624#issuecomment-393708381 using your GitHub account

Received on Thursday, 31 May 2018 22:56:52 UTC