[whatwg] Canvas Proposal: aliasClipping property
robert at ocallahan.org
Thu Oct 8 15:10:44 PDT 2009
On Fri, Oct 9, 2009 at 10:51 AM, Charles Pritchard <chuck at jumis.com> wrote:
> Here is a good example of the conflict between Google and Mozilla over
> There is another conflict, with the composition modes between the two, with
> again taking another principled stand. I'm sorry I don't supporting links
> for that,
> but it effects many of the composite operations (at least four of them).
> I'm hoping to have both methods supported, I think they are both valuable.
> I've certainly used both methods in my work the past few years.
> This is very much about the clipping pipeline.
No, it is entirely about antialiasing. Coverage-based antialiasing causes
problems whenever you draw two objects with adjacent edges that aren't
aligned to pixel boundaries. It doesn't matter whether those boundaries are
induced by clipping or just by filling a path. The post you linked to even
refers to this:
The second problem with anti-aliasing, even when done correctly, is that it
> makes it impossible to put polygons next to each other. Try this demo<http://tulrich.com/geekstuff/canvas/perspective.html>in Firefox and note the hairlines caused by anti-aliasing.
Personally I'm not a big fan of coverage-based antialiasing for exactly this
reason, but it's the most common antialiasing technique in graphics
libraries so it's hard to get away from.
"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