- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Dec 2022 08:23:21 +0000
- To: public-css-archive@w3.org
> [...] defining them as **aliases** of `crisp-edges and smooth` [...] should it **map** to the new `high-quality` keyword? I am sorry for the following aside/question but should it be aliases or mappings? FF handles them as aliases (Chrome does not support the CSS property). The spec suggests a mapping: > a user agent must accept them as valid values but must treat them as having the same behavior [...] Mapped values are preserved and aliases are replaced, iiuc. I do not know when/why a legacy value should be aliased vs. mapped, or if consistency does not matter to you for this kind of minor detail. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8259#issuecomment-1365706096 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 December 2022 08:23:23 UTC