On 9/23/14 4:24 PM, Jonas Sicking wrote:
This makes the implementation considerably simpler, which is great. It
also means that "pixelated" will essentially just be a
more-interoperable version of "-moz-crisp-edges", for the time being.
Would it make sense to have separate properties for "scale up" and
"scale down"? With image-rendering being a shorthand for setting both?
Maybe.
We use this property in Firefox's UI, to make favicons look better when
upscaling on hidpi displays... NN upscaling looks better for tiny icons,
because "smooth" algorithms just make them look blurry. I noted in bug
839923 comment 0 that it's not ideal to have the same behavior for
downscaling, and the issue tangentially came up again in bug 1041845.
So there's a plausible use case. OTOH, scaling tiny icons is just
generally not good with either algorithm, so having the capability isn't
really of much use. There are other scaling algorithms explicitly
designed to scale small/pixel-art images much better, but AFAIK no
browser actually implements such a thing.
Justin
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
