[Bug 13181] New: Canvas does not allow mouse events to be directed to keyboard accessible objects in fallback content

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13181

           Summary: Canvas does not allow mouse events to be directed to
                    keyboard accessible objects in fallback content
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: HTML Canvas 2D Context (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,
                    public-html@w3.org


This is an annoying problem with canvas. You have to have to apply keyboard and
and mouse handlers on entirely different objects. The keyboard handler can be
applied to a fallback content element that it belongs to, yet the pointing
device handlers have to be applied to an entirely different element <canvas>
for all the drawing objects in canvas. 

This could be addressed by creating defining drawing paths in canvas and
binding them to canvas fallback content that they are associated with. The
pointing device events could be dispatched to the fallback content element in
response to a hit. If the drawing paths were assigned a z-order a simple
pointInPath() call could be used to assess the hit. If no path is hit the event
would pass down to the canvas element just as it does today. 

See the related bug: http://www.w3.org/Bugs/Public/show_bug.cgi?id=13176

-- 
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 Thursday, 7 July 2011 22:43:28 UTC