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 10133 - Use of this element requires passing a contextID string to getContext, but the standard does prescribe either (a) an enumeration of valid contextIDs or (b) a method to enumerat the contextIDs supported by a given UA. (b) should be a requirement of the sta
Summary: Use of this element requires passing a contextID string to getContext, but th...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (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-07-11 19:33 UTC by contributor
Modified: 2010-10-04 14:28 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-07-11 19:33:43 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-canvas-element

Comment:
Use of this element requires passing a contextID string to getContext, but the
standard does prescribe either (a) an enumeration of valid contextIDs or (b) a
method to enumerat the contextIDs supported by a given UA. (b) should be a
requirement of the standard

Posted from: 74.75.67.59
Comment 1 Ian 'Hixie' Hickson 2010-08-30 19:00:00 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: Rejected
Change Description: no spec change
Rationale: There's only two valid ones (they're listed in a wiki page referenced from the spec). Just try each one in turn if you actually have code that can use one or the other.