Re: [csswg-drafts] [css-contain] Computed value of shortcut values (#5511)

One solution for that is to add a note to step 2 of the serialization algorithm to handle that case. Something like

> If either of the above syntactic translations would be less backwards-compatible or doesn't have a distinct representation, do not perform them.

With that addition in place, the longhand values are kept in case two representations conflict.


GitHub Notification of comment by SebastianZ
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 15 September 2020 20:38:45 UTC