I've editted the spec to reflect the point in (1): > Specified values of [=custom properties=] must be serialized > <em>exactly as specified by the author</em>. > Simplifications that might occur in other properties, > such as dropping comments, > normalizing whitespace, > reserializing numeric tokens from their value, > etc., > must not occur. > > Computed values of [=custom properties=] must similarly be serialized > <em>exactly as specified by the author</em>, > save for the replacement of any ''var()'' functions. Along with an example and some reasoning for this (I remember the UUID case being brought up earlier). I don't think this change has been approved by the WG, but it's implemented that way in Gecko (and possibly now in Chrome?) so I suspect it'll be a nice easy rubber-stamp. Tagging Agenda+ to get the resolution tho. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5685#issuecomment-885309696 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Thursday, 22 July 2021 23:55:45 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:39 UTC