- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Dec 2022 17:39:50 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-images-3] Is "image-rendering: crisp-edges" still worthwhile to keep separate?`, and agreed to the following: * `RESOLVED: Revert the definition of crisp edges to allow for more advanced algorithms` <details><summary>The full IRC log of that discussion</summary> <flackr> TabAtkins: fantasai pointed out this needs a resolution. I took it on editors discretion, dholbert agreed on this. image-rendering controls how images are upscaled / downscaled has a combination of value that vaguely try to keep things pixelated<br> <flackr> TabAtkins: pixelated, crisp-edges and nearest edges<br> <flackr> TabAtkins: we ended up deciding that ?? allowed slightly blurred edges. There was also nearest which could result in slightly different sizes because of grid mismatches<br> <astearns> s/??/pixelated/<br> <flackr> TabAtkins: and nearest edges allowed for higher quality resampling. Nobody bit and implemented so I propose merging crisp-edges and nearest-neighbor<br> <flackr> TabAtkins: I removed crisp-edges and defined it to be equivalent to nearest-neighbor which keeps edges crisp even if resized a little<br> <flackr> chris_: I think this is right thing to do, the intent was for crisp-edges to do nearest neighbor<br> <astearns> ack fantasai<br> <flackr> fantasai: I don't like this change, because crisp-edges to me suggests you get crisp looking edges rather than jagged edges on diagonal lines<br> <flackr> fantasai: there's lots of art for which this isn't appropriate. I.e. you want something upscaled in a way to maintain edge boundaries<br> <flackr> fantasai: I can see a reason to want nearest neighbor but think this should just be called nearest neighbor since that's what you're requesting<br> <flackr> TabAtkins: the edges are exceedingly crisp, jaggedness was present in original image<br> <smfr> q+<br> <flackr> fantasai: I feel the name doesn't imply make this roughly pixelated<br> <flackr> fantasai: i think we could do better<br> <flackr> astearns: is crisp edges something we have to support for web compat?<br> <flackr> TabAtkins: moz has it prefixed, maybe still, not sure about other impls<br> <astearns> ack smfr<br> <flackr> smfr: I think browser want to map crisp edges to pixelated because that's easier, but maybe now with machine learning algorithms we'd have better ways to upscale line art and keep the door open to use these options<br> <fantasai> +1 crisp-edges seems to me like it would be appropriate for line art<br> <flackr> TabAtkins: i'm fine either way, can define to be flexible or not<br> <flackr> TabAtkins: if we leave it open, do we leave nearest neighbor as an explicit algorithm, or have a value that's something like nearest neighbor<br> <flackr> fantasai: I think for most people they'd be happy with pixelated which does almost this<br> <flackr> TabAtkins: I suspect so as well<br> <fantasai> with better handling of non-integer multiples<br> <flackr> TabAtkins: proposal is that we partially revert, keep the merging of crisp edges and nearest neighbor, default to nearest neighbor but allow impls to use better algorithms<br> <flackr> fantasai: i think the text before did this more nicely<br> <flackr> TabAtkins: problem was it referenced nearest neighbor algo<br> <flackr> fantasai: we can put that as a definition in the property and reference from two values<br> <flackr> TabAtkins: agreed<br> <flackr> fantasai: i'm happy with crisp edges with original definition<br> <flackr> RESOLVED: Revert the definition of crisp edges to allow for more advanced algorithms<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6038#issuecomment-1341332452 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 December 2022 17:39:52 UTC