[Bug 12410] New: fillText needs stricter definitions so that it's 100% uniform

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12410

           Summary: fillText needs stricter definitions so that it's 100%
                    uniform
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: HTML Canvas 2D Context (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: warcraftthreeft@sbcglobal.net
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


I tried to say this before about the problems with bilinear vs nearest neighbor
rendering with images, but I think that Canvas 2D should define what fillText
does in a stricter way so that it is more uniform across browsers.

Here's a simple pixel font example using a truetype font
http://assaultwars.com/javascript/fontface.html

IE9 currently handles this in a very sane way. It renders without cleartype
support when using fillText which I believe should be the defined standard.
That is when you render text it should fill the text with exactly the color you
define without applying transformations for LCD striping (by using patented
techniques).

Currently things look like this on each major browser:
IE9:
http://assaultwars.com/pictures/04b_03ComparisonIE9.png
http://assaultwars.com/pictures/04b_03ComparisonIE9Magnified.png
Chrome 10:
http://assaultwars.com/pictures/04b_03ComparisonChrome10.png
http://assaultwars.com/pictures/04b_03ComparisonChrome10Magnified.png
FF4:
http://assaultwars.com/pictures/04b_03ComparisonFF4.png
http://assaultwars.com/pictures/04b_03ComparisonFF4Magnified.png

This would also allow pixel fonts to be legible since they're currently not in
most browsers.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 2 April 2011 03:58:03 UTC