- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Wed, 26 Jun 2013 13:07:48 -0500
- To: cam@mcc.id.au, Erik Dahlstrom <ed@opera.com>
- Cc: "public-svg-wg@w3.org"@us.ibm.com
- Message-ID: <OFEC4693F4.07B2E60E-ON86257B96.0060B408-86257B96.00639716@us.ibm.com>
Hi Erik, You might add this to day's agenda or we can discuss it on the list. I am working towards my action item of getting the programmable javascript functions in for keyboard support. Specifically, today I updated SVGElement to support the HTMLElement features: - focus() - blur() - the tabindex property At this point I have definitions for each that align with the HTML spec with the exception of tabindex. I found an error in the HTML5 spec. pertaining to the value of -1. This the current definition I have in SVGElement for tabindex: The tabIndex attribute must reflect the value of the tabindex content attribute. Its default value is 0 for elements that are directly focusable, such as through keyboard tabbing in browsers that support that functionality, and ?1 for elements that are not focusable without programmatic intervention. However, HTML5 has this definition in section 7.4.1 of the HTML5 CR spec: "The tabIndex IDL attribute must reflect the value of the tabindex content attribute. Its default value is 0 for elements that are focusable and ?1 for elements that are not focusable." In HTML5, a tabindex of -1 would indicate that the element is focusable but the element could only receive use of focus through the use of script. So, a value of -1 means that the element is indeed focusable vs "not focusable." The HTML5Element IDL is here: http://www.w3.org/TR/2012/CR-html5-20121217/dom.html#htmlelement and the tabindex property is linked to the definition here: http://www.w3.org/TR/2012/CR-html5-20121217/editing.html#dom-tabindex Questions: 1. Does the group agree with the revised wording and how should who should coordinate the definition with the HTML working group. The value returned by the user agent does not change but it does require greater clarity. So, HTML5 CR results will not change. 2. Does the group want me to include a click() function in SVGElement? This would also move focus if the element were focusable. 3. Would the group like me to add HTML5 processing on the focus() and blur () functions for these SVGElement operations to our spec? http://www.w3.org/TR/2012/CR-html5-20121217/editing.html#element-level-focus-apis I will be working to add the Document level APIs from HTML next: http://www.w3.org/TR/2012/CR-html5-20121217/editing.html#document-level-focus-apis Cheers, Rich
Received on Wednesday, 26 June 2013 18:09:06 UTC