On Mon, Jun 30, 2008 at 7:30 PM, Ian Hickson <ian@hixie.ch> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">On Mon, 30 Jun 2008, Vladimir Vukicevic wrote:<br>
> On Jun 11, 2008, at 3:34 AM, Ian Hickson wrote:<br>
> > On Mon, 2 Jun 2008, Vladimir Vukicevic wrote:<br>
> > ><br>
> > > I'd like to propose adding an imageRenderingQuality property on the<br>
> > > canvas 2D context to allow authors to choose speed vs. quality when<br>
> > > rendering images (especially transformed ones).<br>
> ><br>
> > How can an author know which is appropriate?<br>
><br>
> Erm, presumably because they're the author -- it seems quite valid to<br>
> for an author to be able to say "Just make this happen quickly, I don't<br>
> care about the quality" or "Take extra time to make this the highest<br>
> quality you can".<br>
<br>
</div></div>It seems better for the browser to simply detect when the graphics burden<br>
being placed on the hardware by the page is too much to be done at high<br>
quality given the current load on the CPU, and for the browser to<br>
automatically drop down to a lower fidelity, higher speed rendering on the<br>
fly when appropriate.<br>
</blockquote></div><br>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.<br>
<br>