- From: Cameron McCormack <cam@mcc.id.au>
- Date: Mon, 31 Oct 2011 11:53:14 -0700
- To: www-svg@w3.org, Rik Cabanier <cabanier@gmail.com>
- CC: mbostock@cs.stanford.edu
On 31/10/11 11:44 AM, Rik Cabanier wrote: > do you consider these bugs in the browser or do you want to see the SVG > spec specify better how things should be rendered? > The spec already defines some keywords to address your issue. See > shape-rendering in http://www.w3.org/1999/07/06/WD-SVG-19990706/render.html > Some browsers also have the crisp edges keyword to turn off antialiasing > on the entire SVG file. We did accept a requirement for SVG2 to improve the situation with seams between elements. I wonder whether the super path proposal (or whatever solution we end up with for shared path edges) can help here, so that the implementation can be aware of what paths will result in full coverage of particular pixels. I am not sure we want to go down the path of requiring FSAA with particular properties like shape-rendering -- if implementations are hardware accelerated and want to enable FSAA then I think they should just be able to.
Received on Monday, 31 October 2011 18:56:12 UTC