This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10927 - collection of all interactive (actionable, focusable) elements
Summary: collection of all interactive (actionable, focusable) elements
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Cynthia Shelly
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2010-10-01 00:53 UTC by Cynthia Shelly
Modified: 2011-01-11 18:04 UTC (History)
7 users (show)

See Also:

Attachments

Description Cynthia Shelly 2010-10-01 00:53:30 UTC 
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.
Comment 1 Cynthia Shelly 2010-10-01 00:57:16 UTC 
perhaps the list in 3.2.5.1.7 Interactive content is the right set of things to include in the collection?
Comment 2 Ian 'Hixie' Hickson 2010-10-05 00:46:53 UTC 
Could you give an example of a script that would use such an API? I don't understand the use case.
Comment 3 Ian 'Hixie' Hickson 2010-10-12 07:29:49 UTC 
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
Comment 4 Martin Kliehm 2011-01-11 18:04:23 UTC 
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.