10927 2010-10-01 00:53:30 +0000 collection of all interactive (actionable, focusable) elements 2011-01-11 18:04:23 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Windows NT RESOLVED NEEDSINFO a11y P2 normal --- 1 cyns cyns ian laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 40352 0 cyns 2010-10-01 00:53:30 +0000 It would be useful to have a collection of the elements on a page that the user can interact with. this is similar the HTMLFormControlsCollection, except that it would also include interactive elements from 4.11 and links from 4.12, and could be gathered from any parent element, not just form and fieldset. It would be nice to be able to include elements whose ARIA role would make them interactive, that contain @tabindex!=-1, or that have event handlers associated with them as well. However some of those might be harder. Having this colleciton would allow authors to easily find the interactive elements, rather than having to test for specific element types or roles. 40353 1 cyns 2010-10-01 00:57:16 +0000 perhaps the list in 3.2.5.1.7 Interactive content is the right set of things to include in the collection? 40607 2 ian 2010-10-05 00:46:53 +0000 Could you give an example of a script that would use such an API? I don't understand the use case. 40990 3 ian 2010-10-12 07:29:49 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: see comment 2 44169 4 w3c 2011-01-11 18:04:23 +0000 The bug-triage sub-team doesn't think this is a TF priority. We do think the bug should have been clear, though Ian marked "do not understand". Assigning to Cynthia to follow up.