- From: Mark Sadecki <mark@w3.org>
- Date: Tue, 15 Apr 2014 16:01:00 -0400
- To: "public-canvas-api@w3.org" <public-canvas-api@w3.org>, "Rik Cabanier (cabanier@adobe.com)" <cabanier@adobe.com>, Jatinder Mann <jmann@microsoft.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Jay Munro <jaymunro@microsoft.com>
This was not discussed on the call last night, but I wanted to run it by you for consideration: ## hit region definition http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas_CR/#hit-region * Move the note found in the addHitRegion definition that reads > "NOTE: While both ID and control are optional, when calling addHitRegion, at least one of the two needs to be present to create a hit region. " above the definition box so that it follows the section where we actually say that both ID and control are optional. It would read as follows: [snip] * Optionally, a non-empty string representing an ID for distinguishing the region from others. * Optionally, a control. A control is a reference to an Element node, to which, in certain conditions, the user agent will route events, and from which the user agent will determine the state of the hit region for the purposes of accessibility tools. (The control is ignored when it is not a descendant of the canvas element.) NOTE: While both ID and control are optional, when calling addHitRegion, at least one of the two needs to be present to create a hit region. -- Mark Sadecki Web Accessibility Engineer World Wide Web Consortium, Web Accessibility Initiative Telephone: +1.617.715.4017 Email: mark@w3.org Web: http://w3.org/People/mark
Received on Tuesday, 15 April 2014 20:01:02 UTC