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 11263 - Most browsers seem to clear to transparent -white- by default, since this results in much nicer blended edges in antialiased-graphics.
Summary: Most browsers seem to clear to transparent -white- by default, since this res...
Status: RESOLVED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML Canvas 2D Context (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-08 16:04 UTC by contributor
Modified: 2011-08-04 05:03 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-11-08 16:04:54 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#simple-shapes-(rectangles)

Comment:
Most browsers seem to clear to transparent -white- by default, since this
results in much nicer blended edges in antialiased-graphics. 

Posted from: 82.170.157.116
Comment 1 Ian 'Hixie' Hickson 2010-12-29 08:28:21 UTC 
Do you have a test case demonstrating this?
Comment 2 Ian 'Hixie' Hickson 2011-01-21 02:11:21 UTC 
Philip`: Can you comment on this?
Comment 3 Philip Taylor 2011-01-21 02:31:25 UTC 
Most browsers use premultiplied alpha so transparent white and transparent black both get encoded as (0,0,0,0) which gets decoded into rgba(0,0,0,0) - they can never distinctly represent transparent white. It shouldn't affect correctly-implemented antialiasing either way, anyway. I guess it's most likely that the original reporter was confused.
Comment 4 Ian 'Hixie' Hickson 2011-02-11 01:31:27 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:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: Short a testcase demonstrating the issue, I'm at a loss as to how to evaluate this proposal, and my go-to guy for <canvas> was unable to divine the reporter's intent either.
Comment 5 Michael[tm] Smith 2011-08-04 05:03:37 UTC 
mass-move component to LC1