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 24713 - some <th> elements and most elements with tabindex="" should probably count as interactive
Summary: some <th> elements and most elements with tabindex="" should probably count a...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks: 24750
  Show dependency tree / graph
 
Reported: 2014-02-18 20:21 UTC by contributor
Modified: 2014-02-20 23:38 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2014-02-18 20:21:01 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#interactive-content
Complete: http://www.whatwg.org/c#interactive-content
Referrer: 

Comment:
some <th> elements and most elements with tabindex="" should probably count as
interactive

Posted from: 2620:0:1000:167c:b1bc:1289:55f0:5f5e by ian@hixie.ch
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1809.0 Safari/537.36
Comment 1 Ian 'Hixie' Hickson 2014-02-18 21:12:40 UTC 
While I'm at it, elements that would otherwise not be focusable but are because of an explicit tabindex="" attribute should probably be ok in <canvas> and hit regions, since they're basically just buttons at that point. (Without such a change, making tabindex="" set an element to interactive would mean it was no longer allowed in <canvas>.)