16018 2012-02-17 17:36:44 +0000 Exclude disabled form controls from specially focusable elements. 2012-11-01 23:07:09 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#focusable P3 normal Unsorted 1 contributor ian hans.hillen ian kennyluck lwatson mike contributor oldest_to_newest 64244 0 contributor 2012-02-17 17:36:44 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html Multipage: http://www.whatwg.org/C#focusable Complete: http://www.whatwg.org/c#focusable Comment: Exclude disabled form controls from specially focusable elements. Posted from: 114.25.240.243 by kennyluck@csail.mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/534.51.22 (KHTML, like Gecko) Version/5.1.1 Safari/534.51.22 64245 1 kennyluck 2012-02-17 17:46:05 +0000 This paragraph doesn't exclude disabled form controls that have tabindex specified. In the following test case "onfocus" doesn't appear in IE9, Firefox 10, Safari 5 and Chromium 18 data:text/html,<!DOCTYPE html><textarea tabindex="0" disabled onfocus='document.write("onfocus");'>CLICK</textarea><script>document.querySelector('textarea').focus()</script> (Opera12alpha is a bit special but that has nothing to do with 'tabindex'. It fires the 'focus' event for disabled form controls when focus() is called, which is not following the spec.) I think in general this paragraph should exclude all elements :disabled matches. Test case: data:text/html,<!DOCTYPE html><fieldset disabled><textarea tabindex="0" onfocus='document.write("onfocus");'>CLICK</textarea></fieldset><script>document.querySelector('textarea').focus()</script> Firefox follows my expectable but IE9 and WebKit browsers don't. That's because they don't implement 'disabled' on <fieldset>. 70599 2 contributor 2012-07-18 16:20:00 +0000 This bug was cloned to create bug 18065 as part of operation convergence. 72960 3 ian 2012-08-29 03:33:19 +0000 So what I need to do here is factor out the :disabled list into a reusable term "disabled element", label the current list of what makes something by-default focusable the "suggested focusable elements", remove all the stuff about "disabled" in the current definition of the "suggested focusable elements", then in the definition of "focusable" refer to the "suggested focusable elements" instead of the platform conventions, and then add an explicit filter to remove the "disabled elements". 77721 4 contributor 2012-11-01 23:07:09 +0000 Checked in as WHATWG revision r7498. Check-in comment: Another attempt at defining tabindex, :disabled, what can be focused, etc. http://html5.org/tools/web-apps-tracker?from=7497&to=7498