On Wed, Sep 24, 2014 at 7:21 PM, Daniel Holbert <dholb...@mozilla.com> wrote:
> On 09/24/2014 07:38 AM, Ehsan Akhgari 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. > > > > So, what are we planning to do with -moz-crisp-edges? > > I'm not aware of any specific plans to change it at the moment. > > > I think keeping it in its current form may be pointless (unless if we > > know this is something that the Web depends on?) > > It's unclear to me whether the web depends on it. As a proxy, we use it > in 16 places within /browser. > > Moreover, note that this behavior is *only* available using per-browser > prefixed keywords; so I doubt authors have unprefixed fallback at this > point. So, unprefixing or removing "-moz-crisp-edges" would likely > break content at this point. (I'll bet authors will start including > unprefixed "pixelated" soon, though, because that'll be the only way to > get this behavior in Chrome, once it ships there.) > > > If I'm reading the > > spec correctly, we can actually unprefix it and make it equivalent to > > pixelated, but I'm not sure how valuable that is. > > We probably do want to eventually unprefix -moz-crisp-edges (and as you > say, we *could* do so now), but if we're planning to tweak which > algorithm we use (unclear), it might be wise to wait until we've done > that before unprefixing. > > > I think that this is > > allowed by the spec though, so perhaps it should be modified to say how > > crisp-edges must be different than pixelated. > > They don't have to be different. As Tab said on the Blink > intent-to-implement thread: > > Having "crisp-edges" act like "pixelated" is an > allowed implementation strategy. It's also allowed, > though, to be smarter when doing "crisp-edges", and > use an intelligent pixel-scaling algorithm, of > which there are many. > > "pixelated" was added by request of multiple users, who sometimes > literally want the "big pixel" look of plain nearest-neighbor > interpolation. > FWIW, NN interpolation is used by a lot of Flash content for the same reason, which is why implementing it was pretty high priority in Shumway. Given that, it's pretty likely that there's quite a bit of interest among web designers, too. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
