[whatwg] Canvas Proposal: aliasClipping property

This sounds like a very good proposal, but can we extend it to include other
things than just drawImage? I'm not sure how useful it would be, but it
could perhaps include all the other drawing options, like stroking and
filling paths created with lineTo, arc, etc.

Marius Gundersen

On Sun, Oct 4, 2009 at 9:10 AM, Charles Pritchard <chuck at jumis.com> wrote:

> There have been a few discussions about anti-aliasing / aliasing in Canvas
> implementations.
> Of those I read through, the conflict remains.
>
> In some implementations: when drawImage is used along with a clipping path,
> feathering is applied. This shows up in several projective transformation
> demos
> contrasting Firefox with Chrome.
>
> I believe that if we allow a toggle for this setting, we can bring some
> compatibility
> to the two systems.
>
> Enumerate two aliasClipping values : "aliased", "feathered"
>
> I consider "anti-aliased" to confusing, I think "feathered" is a better
> name.
>
> .....
>
> [Supplemental]
> interface CanvasRenderingContext2D {
>    attribute DOMString aliasClipping; // default "feathered"
>  }
>
> context . aliasClipping [ = value ]
>
>    Returns the current aliasing of the clipping region, as applied to
> rendering operations.
>
>    Can be set, to change the aliasing value.
>
>    If any of the arguments are not implemented, throws a NOT_SUPPORTED_ERR
> exception.
>
> CanvasRenderingContext2D.prototype.defineSetter('aliasClipping') { throw
> NOT_SUPPORTED_ERR; }
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20091004/96c76cef/attachment.htm>

Received on Saturday, 3 October 2009 18:34:44 UTC