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

Re: [whatwg] Blurry lines in 2D Canvas (and SVG)

From: Ruben Rodriguez II <whatwg@therealcha0s.net>
Date: Fri, 27 Sep 2013 16:13:19 -0500
Message-ID: <5245F4EF.5040407@therealcha0s.net>
To: whatwg@lists.whatwg.org
It seems like those should be two separate things instead of lumped all 
together in a monolithic "You can do this if you want... or whatever!"

"Snapping" is definitely something different than antialiasing. It's a 
huge pain for anyone trying to provide a(n accurate) simple 2D primitive 
library.

On 07/23/2013 08:16 PM, Rik Cabanier wrote:
> I guess there's too many "might"s in there :-)
>
> I want to "adjust line positions and line widths to align edges with device
> pixels" but not "the user agent might turn off anti-aliasing for all lines
> and curves"
>
> On Tue, Jul 23, 2013 at 6:11 PM, Brian Birtles <bbirtles@mozilla.com> wrote:
>
>> (2013/07/24 10:07), Rik Cabanier wrote:
>>
>>> yeah, at first blush that seemed what was needed.
>>> However, this simply turns off antialiasing completely so regular
>>> artwork looks terrible.
>>>
>> That's a quality of implementation issue. The description of the property
>> value says,
>>
>> "Indicates that the user agent shall attempt to emphasize the contrast
>> between clean edges of artwork over rendering speed and geometric
>> precision. To achieve crisp edges, the user agent might turn off
>> anti-aliasing for all lines and curves or possibly just for straight lines
>> which are close to vertical or horizontal. Also, the user agent might
>> adjust line positions and line widths to align edges with device pixels."
>>
>> I'm not sure what use case you have in mind though. Perhaps it's something
>> that doesn't fit that description?
>>
>>
Received on Friday, 27 September 2013 21:16:00 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:09 UTC