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 9190 - What effects do fillText and strokeText have on the accessibility fallback (ADOM?)? Should they take a default to also adding it, as by canvas.appendChild(document.createTextNode(s))? (Then maybe add a 5th parameter to allow turning it off) -jJ
Summary: What effects do fillText and strokeText have on the accessibility fallback (A...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML Canvas 2D Context (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
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-03-04 21:27 UTC by contributor
Modified: 2010-10-05 12:58 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-03-04 21:27:28 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#text

Comment:
What effects do fillText and strokeText have on the accessibility fallback
(ADOM?)?  Should they take a default to also adding it, as by
canvas.appendChild(document.createTextNode(s))?  (Then maybe add a 5th
parameter to allow turning it off) -jJ

Posted from: 32.97.110.59
Comment 1 Ian 'Hixie' Hickson 2010-03-30 02:52:49 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: I don't think that would make sense given the way canvas generally is expected to be used. In fact, I can't really think of any case where you would want that. If you have any concrete examples where each time fillText() is called, text is placed somewhere in the fallback, please let me know. I'd love to study the design patterns that lead to such a scenario; it might provide insight into other things we could do too.

In the absence of such an example, though, I haven't changed the spec.