- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Sep 2020 20:38:42 +0000
- To: public-css-archive@w3.org
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-config
Received on Tuesday, 15 September 2020 20:38:45 UTC