- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Sat, 03 Dec 2022 17:36:55 +0000
- To: public-css-archive@w3.org
If I understand correctly, it says that they are mapped whereas the current syntax suggests that they are aliases. > These are now deprecated; a user agent must accept them as valid values but must treat them as having the same behavior as `crisp-edges` and `smooth` respectively If I am not mistaken, mapped values are preserved (for serialization) whereas aliases are replaced at parse time. I guess the difference is not important for implementers. Maybe CSS authors would prefer aliases, so they know they are using a legacy value. But how various legacy rules/properties/functions are handled (aliased or mapped) is inconsistent and this creates [confusion](https://github.com/whatwg/compat/issues/220). -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8173#issuecomment-1336204602 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 3 December 2022 17:36:57 UTC