- From: Rik Cabanier <cabanier@gmail.com>
- Date: Sun, 16 Dec 2012 20:52:33 -0800
- To: Justin Novosad <junov@chromium.org>
- Cc: whatwg@lists.whatwg.org, Jeff Muizelaar <jmuizelaar@mozilla.com>, Vladimir Vukicevic <vladimir@pobox.com>, Ian Hickson <ian@hixie.ch>, Kevin Gadd <kevin.gadd@gmail.com>
On Wed, Dec 12, 2012 at 10:24 AM, Justin Novosad <junov@chromium.org> wrote: > > > On Wed, Dec 12, 2012 at 12:39 PM, Rik Cabanier <cabanier@gmail.com> wrote: > >> >> What would be the next step? Should we define a new version of drawImage >> with the extra parameter? > > > That is one option, but I think a context attribute (like > imageSmoothingEnabled) is also worth considering. > Perhaps image smoothing could be an enum rather than boolean with an > additional mode that prevents color bleeding. > It seems a bit too expensive to add a variable to the graphics context that is checked for just this call. Maybe just a new drawImage call (like drawNonSmoothedImage?) is all that is needed. > > >> If so, we probably want the description of the existing drawImage call to >> change so it leaves the resampling issue undefined unless WebKit is OK with >> changing their current behavior. >> > > IMHO: Undifined behavior is a spec bug. If we have a problem with the > spec, we fix the spec, we don't just each do our own thing. > >
Received on Monday, 17 December 2012 04:53:02 UTC