Re: [csswg-drafts] [css-images-3] Define optimizeSpeed as nearest neighbor (#8259)

The CSS Working Group just discussed `[css-images-3] Define optimizeSpeed as nearest neighbor`, and agreed to the following:

* `RESOLVED: close, no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> fantasai: We have SVG values that correspond to SVG keywords<br>
&lt;emeyer> …It was observed browsers might be able to use better algorithms<br>
&lt;emeyer> …Should optimizeSpeed be the same as crispEdges?<br>
&lt;emeyer> TabAtkins: These legacy values are only around because I’m reusing names from SVG<br>
&lt;emeyer> …As far as I know, no browser ever did anything with them<br>
&lt;emeyer> …Other renderers might, not sure<br>
&lt;emeyer> …For the web, it doesn’t seem like it matters what we map them to<br>
&lt;emeyer> …I do object to adding bespoke behavior for these values<br>
&lt;emeyer> …If we want to do something with nearest-neightbor, we should do that<br>
&lt;emeyer> …If we do want to do that later, it would be fine to swap mapping<br>
&lt;emeyer> …For now, what exact value we define isn’t important<br>
&lt;emeyer> …I suggest we close, no change<br>
&lt;emeyer> fantasai: I think it’s an okay state for now, but is risky in the long run<br>
&lt;emeyer> …If there are people who would want nearest-neighbor, maybe we should add a keyword specifically for that<br>
&lt;emeyer> TabAtkins: I’m happy to switch the alias over in that case, but don’t want to do anything special for it now<br>
&lt;emeyer> fantasai: Seem fine; do we need a `nearest-neightbor` keyword?<br>
&lt;emeyer> TabAtkins: That woul db e a different issue<br>
&lt;emeyer> astearns: Proposed resolution is close, no change for now; can discuss separately if we need `nearest-neighbor` or any other<br>
&lt;emeyer> …At that point we could discuss whether to change the alias for `optimizeSpeed`<br>
&lt;emeyer> astearns: Objections?<br>
&lt;emeyer> RESOLVED: close, no change<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8259#issuecomment-1515037822 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 19 April 2023 16:31:30 UTC