W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2008

[whatwg] [canvas] imageRenderingQuality property

From: Mark Finkle <mark.finkle@gmail.com>
Date: Mon, 30 Jun 2008 19:55:33 -0400
Message-ID: <8e61feeb0806301655o51f68d62s6aa28fbd04ca946b@mail.gmail.com>
On Mon, Jun 30, 2008 at 7:30 PM, Ian Hickson <ian at hixie.ch> wrote:

> On Mon, 30 Jun 2008, Vladimir Vukicevic wrote:
> > On Jun 11, 2008, at 3:34 AM, Ian Hickson wrote:
> > > On Mon, 2 Jun 2008, Vladimir Vukicevic wrote:
> > > >
> > > > I'd like to propose adding an imageRenderingQuality property on the
> > > > canvas 2D context to allow authors to choose speed vs. quality when
> > > > rendering images (especially transformed ones).
> > >
> > > How can an author know which is appropriate?
> >
> > Erm, presumably because they're the author -- it seems quite valid to
> > for an author to be able to say "Just make this happen quickly, I don't
> > care about the quality" or "Take extra time to make this the highest
> > quality you can".
>
> It seems better for the browser to simply detect when the graphics burden
> being placed on the hardware by the page is too much to be done at high
> quality given the current load on the CPU, and for the browser to
> automatically drop down to a lower fidelity, higher speed rendering on the
> fly when appropriate.
>

So now we need to define levels of graphic burden? and at what level of
burden does the quality suffer? Seems just as hard to define. Having the
author explicit say "this has to be as high quality as possible" or "less
can be low quality" seems better and we have examples of other specs
offering the same kind of control.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20080630/3619f0b3/attachment.htm>
Received on Monday, 30 June 2008 16:55:33 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:03 UTC