- From: Justin Novosad <junov@google.com>
- Date: Fri, 14 Mar 2014 14:40:39 -0400
- To: Ian Hickson <ian@hixie.ch>
- Cc: WHATWG <whatwg@lists.whatwg.org>
On Fri, Mar 14, 2014 at 2:29 PM, Ian Hickson <ian@hixie.ch> wrote: > > > I scale down images using context.drawImage. There is no way for me to > > opt in for which filter method to use. I thought it was a bug first, > > because I thought context.webkitImageSmoothingEnabled did the job. But > > it didn't. So I filed a bug for chrome. But they suggested me to email > > you guys. > > > > https://code.google.com/p/chromium/issues/detail?id=326640 > > If the bug is that Chrome resamples the image in an ugly way, then that's > a bug with Chrome. As the bug says, browsers are allowed to pick whatever > algorithm they want -- it's a quality-of-implementation issue. But if the > result is ugly, that's a low quality implementation. > Yes, and if we fixed it to make it prettier, people would complain about a performance regression. It is impossible to make everyone happy right now. Would be nice to have some kind of speed versus quality hint.
Received on Friday, 14 March 2014 18:41:05 UTC