issues.md

Issues filed

This document is used for collecting all the bugs reported and issues raised because of my investigating how focus works and creating ally.js.

Filed browser issues

• Mouse/Touch Events Can Focus Parent Element - WebKit 139945
• Multiple use of same image map hides elements from tabbing sequence - Gecko 1116126
• CSS order property (Flexbox) affects document tabbing sequence - Gecko 1116140
• focus event listener on arbitrary SVGElement makes it focusable - Blink 445798, WebKit 140024
• SVGElement.prototype.focus is missing - Gecko 1116966, Trident 1072662
• empty tabindex [tabindex=""] parsed and exposed as [tabindex="-32768"] - Trident 1072965
• wrong activeElement when focusing element in ShadowDOM - Gecko 1117535
• multiple FocusEvents for focus change within the same ShadowRoot - Gecko 1117544
• positive tabindex elements within ShadowDOM are improperly sorted into document's tabbing sequence - Gecko 1117552
• Implement >>> Selecting Through Shadows Selector for access into shadow root - Gecko 1117572
• Rename "Selecting Through Shadows Selector" from "/deep" to ">>>" - Blink 446051
• sequential navigation failure for negative tabindex on ShadowHost - Blink 446584
• area elements added to document sequential navigation order in DOM order instead of in place of referencing image - Blink 447289, WebKit 140259
• DOM Level 3: FocusEvent sequence - Blink 449857, WebKit 140596, Trident 1092647
• :target element not focused properly when element with autofocus attribute exists - WebKit 140963
• focusing of disabled fieldset element is not prevented - Blink 453847, Webkit 141086
• consecutive object elements break document tabbing order - Trident 1109008
• object element with SVG content is not focusable, with SWF content it is - Trident 1109020
• visible descendants of collapsed table row are not rendered but focused and tabbable - Gecko 1128036
• audio element without valid source is not rendered but focusable - Gecko 1128047
• invalid tabindex value makes element focusable - Gecko 1128054
• Focus Link Target (sequential focus navigation starting point) - Blink 454172, WebKit 141136, Trident 1111056
• element.scrollIntoView() confused by scroll-behavior:smooth; - Gecko 1139745
• audio and video elements with controls cannot be removed from the focus navigation sequence - Blink 512133
• embed element cannot be removed from the focus navigation sequence - Gecko 1185657
• embed element with tabindex="0" breaks sequential focus navigation - Gecko 1195457
• <summary> and <a> within <details open> not keyboard focusable - WebKit 151767
• label element with tabindex attribute is keyboard focusable - Gecko 1240285
• <object> with visibility:hidden should not be focusable - Blink 586191
• Tab focus navigation should not break on hidden SVG - Blink 586200, WebKit 154114
• mutating document.activeElement resets focus to document.body - Blink 660999
• SVG <use> element and elements in <defs> receive keyboard focus - Blink 665121
• SVG link element focus behavior Gecko 1302341
• SVG elements and negative tabindex - Gecko 1302340
• attribute name tabindex vs tabIndex - Edge 9282058

Filed specification issues

• object element usemap should be deprecated
• [Shadow]: how is the autofocus attribute supposed to be handled?
• Sequential Navigation Focus Order for Image Maps
• initial focus precedence: autofocus or fragment identifier
• focusing steps don't contain scrolling an element into view
• [Specifiction] Extending Element-level focus APIs
• "Focus fixup rule one" not very clear, possibly wrong