Re: [whatwg] [canvas] imageRenderingQuality property

2008-07-01 Thread Kristof Zelechovski
The image rendering quality property is indeed unable to hit the tradeoff between beauty of presentation and rendering speed. However, it is perfectly all right to say 'this content is some fancy GUI can be rendered downscaled without degrading the content - but that content contains engineering

Re: [whatwg] [canvas] imageRenderingQuality property

2008-07-01 Thread Oliver Hunt
Yeah, Philip has been slowly convincing me that something like imageRenderingQuality with high and auto values* would be useful, basically for reasons similar to what you just gave. I still don't believe there should be a low option, because (as i have said before) the author is not in a

Re: [whatwg] [canvas] imageRenderingQuality property

2008-07-01 Thread Kristof Zelechovski
Challenge accepted. THIS: the content the author wants the browser to render. HAPPEN: the sequence of operations performed by the browser in order to render THIS. QUICKLY: meeting the user's expectations how long he should wait for THIS. QUALITY: how accurately the browser follows the author's

[whatwg] on ImageData, putImageData() and drawImage()

2008-07-01 Thread Mathieu HENRI
Hi, As of today the variants of the putImageData() method copy a region of an ImageData (in device pixels) straight to a Canvas (in intrinsic pixels) and do not allow to scale the region further than the obvious device to intrinsic scaling. This means that if a developer needs to copy and