Summary: The CSS declaration "image-rendering: pixelated" allows authors to request that we scale up images by effectively making the pixels larger (using a "nearest-neighbor" algorithm). This is in contrast to the default (non-pixelated) scaling behavior, which tends to blur the edges between an image's pixels when upscaling. The default behavior is appropriate for use-cases like photos, but authors may prefer a "pixelated" look e.g. when scaling up pixel-art or favicons.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=856337 Link to standard: http://dev.w3.org/csswg/css-images/#valuedef-pixelated Platform coverage: All Estimated or target release: Firefox 35 or 36 Preference behind which this will be implemented: None. This is a small, targeted feature; if we need to disable it for some reason, we can easily do so with a small change to the CSS parser (just removing the new keyword from the keyword-table for this property). 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. ~Daniel [1] Blink intent-to-implement: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Q8N6FoeoPXI [2] Blink intent-to-ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/zSasd2LL8Mc [3] http://blog.chromium.org/2014/08/chrome-38-beta-new-primitives-for-next.html _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
