This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Canvas introduces a number issues for browser manufacturers when introducing HTML elements that are not rendered in the canvas subtree. We need to asses if there are limitations as to what may be used in the DOM subtree for <canvas>. Currently the specification says very little about the use of the DOM subtree and its association with the <canvas> drawing surface. This needs to be better defined.
Bug triage sub-team agrees this is an A11Y TF priority. However, it is clear this will come back as needsinfo in its current state. Assigning to Rich to address within the canvas sub-team and provide the needed info. Assign to Ian when complete.
Bug triage sub-team thinks this bug is providing additional details on 10964, which was raised just at the Last Call cutoff deadline with the understanding that more precise information would be filed later. This bug constitutes part of that information and therefore we think this should be considered a pre-LC bug. Also note that this bug relates to ISSUE-131 http://www.w3.org/html/wg/tracker/issues/131 and arguably ISSUE-74 http://www.w3.org/html/wg/tracker/issues/74.
Current vendors (webkit/mozilla) are heading toward allowing both script and iframe to be added to the subtree. Microsoft had some concern about iframe; but did not follow up. There's no possibility of 'click-jacking' as the frame would not be visible. I'm investigating allowing canvas elements in the subtree, for accessibility purposes, mainly for screen magnifiers. As far as I understand it, the canvas element follows the rules of other nodes, and this issue is resolved.
Yes. Resolved. Not restricting canvas subtree elements.
mass-moved component to LC1