- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Dec 2022 20:22:28 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-images-3] Define optimizeSpeed as nearest neighbor == The spec preserves the old SVG `optimizeSpeed` and `optimizeQuality` keywords, defining them as alisases of `crisp-edges` and `smooth`. However, in https://github.com/w3c/csswg-drafts/issues/6038 we confirmed that `crisp-edges` is not necessarily nearest neighbor, and that browsers may use a more sophisticated edge-preserving algorithm (which might not be as fast). Would it make sense to simply define `optimizeSpeed` as nearest neighbor? This guarantees its speed and also gives authors direct access to nearest neighbor. Related follow-up: should `optimizeQuality` stay mapped to `smooth` or should it map to the new `high-quality` keyword? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8259 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 December 2022 20:22:30 UTC