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. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5511#issuecomment-692966104 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Tuesday, 15 September 2020 20:38:45 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:16 UTC