[whatwg] [canvas] imageRenderingQuality property
robert at ocallahan.org
Mon Jun 2 15:19:29 PDT 2008
On Tue, Jun 3, 2008 at 9:39 AM, Oliver Hunt <oliver at apple.com> wrote:
> That's exactly what i would be afraid of people doing. If I have a fast
> system why should i have to experience low quality rendering? It should be
> the job of the platform to determine what level of performance or quality
> can be achieved on a given device.
Right, it is. The user-agent is free to map all property values to "maximum
> Typically such a property would be considered a "hint", and as such would
> likely be ignored.
Ignored by who?
Neither of these apply if the property were just a hint, but now you have to
> think about what happens to content that uses this property in 18 months
> time. You've told the UA to use a low quality rendering when it may no
> longer be necessary, so now the UA has a choice it either always obeys the
> property meaning lower quality than is necessary so that new content
> performs well, or it ignores the property in which case new content performs
If the quality knob is no longer necessary, why would new content perform
These hint properties are opt-in for UAs. If you don't like the idea, just
treat all values as "auto".
"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