W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2009

[whatwg] Turn off Anti-Aliasing in Canvas

From: Marius Gundersen <gundersen@gmail.com>
Date: Mon, 14 Sep 2009 17:48:04 +1000
Message-ID: <45f4181c0909140048j101291c2p8c34355ac0f8d839@mail.gmail.com>
This part indicates that it is not implemented because some browsers might
ignore it:

causing browsers that support these features to render
certain sites significantly worse or slower (or both) than browsers who
ignore these flags and instead apply heuristics to determine the optimal
rendering modes.

The composite paths that you indicated sounds cool, but sounds like
something I asked about previously, namely having an explicit method for
redrawing the canvas when the user is done.

Marius Gundersen

On Mon, Sep 14, 2009 at 5:43 PM, Ian Hickson <ian at hixie.ch> wrote:

> On Mon, 14 Sep 2009, Marius Gundersen wrote:
> > >
> > > This has been considered before:
> > >
> > >
> http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2007-May/011263.html
> >
> > so it was decided against because some browsers might not implement it?
>
> No, not at all. What part of that e-mail suggested that it had anything to
> do with browsers not implementing it?
>
>
> > In some cases turning off anti aliasing isn't just about speed or
> > beauty, in some cases it can introduce things that should not be there.
> > For example, notice the white line running diagonally across the face of
> > the crate here:
> > http://www.mariusgundersen.net/projects/Canvas3D/step6.html
>
> The right way to do 3D rendering is not to use a 2D canvas but to use a 3D
> canvas, such as is being developed (in secret, for some reason) by the
> Khronos group.
>
> I agree that sometimes antialiasing leads to seams, though; the solution
> to that isn't to disable antialiasing, though (that would just replace one
> problem with another), the solution is to provide new features that allow
> you to create composite paths that are stroked or filled in one operation
> (with one single antialiasing step) instead of requiring multiple distinct
> operations (each with their own antialiasing).
>
> Such new features will likely be considered for a future version.
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090914/aa81aeb4/attachment.htm>
Received on Monday, 14 September 2009 00:48:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:52 UTC