[whatwg] More random comments on the putImageData definition
robert at ocallahan.org
Sun Feb 10 14:53:54 PST 2008
On Feb 11, 2008 11:37 AM, Oliver Hunt <oliver at apple.com> wrote:
> On Feb 10, 2008, at 2:26 PM, Robert O'Callahan wrote:
> On Feb 10, 2008 10:07 PM, Oliver Hunt <oliver at apple.com> wrote:
> > That said, basically what you're saying is that canvas should not
> > support hidpi. At all. There is no need to request the dpi of a canvas, but
> > (and here's the critical bit) you can't have get/putImageData work at a
> > different resolution from the backing buffer.
> Why not?
> Because the purpose of get/putImageData *is* to get to the device pixels,
> that's their purpose, making them not do that is both bizarre, breaks the
> semantic that putImageData(getImageData(x,y,w,h), x, y) will leave the
> canvas unchanged
Yeah, that makes sense...
> and the cost of sub-/super-sampling removes the whole "speed" thing that
> the API was originally added for.
Not so sure about this. Script manipulation of pixel data probably isn't
going to be faster than native, probably hardware-assisted resampling.
> Yeah, unfortunately we all know the web authors tend to favour the "it
> works now, so must be correct" philosophy -- it's looking more and more like
> i will be forced to convert the canvas from hidpi to 1:1 the moment any of
> the imagedata/toDataURL routines are used. *sigh*
That would break your sensible invariant that
x, y) leaves the canvas unchanged.
It would really suck to lock canvas into a 1:1 device-to-CSS pixel ratio
forever. Seems to me putImageData/getImageData isn't worth that risk. Maybe
we should introduce it later when developers are more likely to encounter
the DPI issues for themselves.
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg