W3C home > Mailing lists > Public > public-html@w3.org > March 2011

[Bug 12214] New: Canvas fallback content implementation is underspecified

From: <bugzilla@jessica.w3.org>
Date: Tue, 01 Mar 2011 20:37:30 +0000
To: public-html@w3.org
Message-ID: <bug-12214-2495@http.www.w3.org/Bugs/Public/>

           Summary: Canvas fallback content implementation is
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: schwer@us.ibm.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,

I spoke with my accessibility contact at Google who spoke to their webkit
developers. They felt this text  to be under specified:

"When a canvas element represents embedded content, the user can still focus
descendants of the canvas element (in the fallback content). This allows
authors to make an interactive canvas keyboard-focusable: authors should have a
one-to-one mapping of interactive regions to focusable elements in the fallback

They felt this left it unclear as to how fallback content should respond to
keyboard input. The suggested adding the following text

"Elements in canvas fallback content should behave as if they were on the page
but invisible and having no effect on layout. Mouse input would go directly to
the canvas because the children do not layout so they have no position to hit

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 1 March 2011 20:37:32 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:33 UTC