On 2014-09-23, 4:53 PM, Daniel Holbert wrote:
NOTES:
- Blink has already implemented "pixelated"[1] and it'll be shipping[2]
in Chrome 38 [3]. So, if & when we ship it, there will be
interoperability between at least 2 engines here. (Other rendering
engines expose similar behavior, albeit under different non-standard
keyword-names.)
- Gecko already has "image-rendering: -moz-crisp-edges" as a way to
request this behavior; the difference is that "-moz-crisp-edges" uses
the same algorithm (nearest-neighbor) regardless of whether it's
upscaling or downscaling, whereas "pixelated" is supposed to *only* use
that algorithm for upscaling, and use the default ("auto") behavior when
downscaling.
Why are upscaling and downscaling treated differently for pixelated?
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
