This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12410 - fillText needs stricter definitions so that it's 100% uniform
Summary: fillText needs stricter definitions so that it's 100% uniform
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML Canvas 2D Context (show other bugs)
Version: unspecified
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: contributor
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2011-04-02 03:57 UTC by Sirisian
Modified: 2011-12-02 17:56 UTC (History)
5 users (show)

See Also:


Description Sirisian 2011-04-02 03:57:59 UTC
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

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:
Chrome 10:

This would also allow pixel fonts to be legible since they're currently not in most browsers.
Comment 1 Michael[tm] Smith 2011-08-04 05:03:51 UTC
mass-move component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-09-21 17:17:53 UTC
Philip, any input on this?
Comment 3 Ian 'Hixie' Hickson 2011-12-02 17:56:13 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

Status: Rejected
Change Description: no spec change
Rationale: I don't really see why this is a canvas problem and not a TrueType problem. As far as Canvas goes, we don't define the anti-aliasing-level rendering detail, because that would be insane and would preclude optimisations for specific display types. If this makes for illegible text, please file bugs with the browsers.