[Webkit-unassigned] [Bug 198730] New: <area> is click and sequentially focusable, but not programatically focusable

Mon Jun 10 14:12:41 PDT 2019

https://bugs.webkit.org/show_bug.cgi?id=198730

            Bug ID: 198730
           Summary: <area> is click and sequentially focusable, but not
                    programatically focusable
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: DOM
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: d at domenic.me

Discussed in the very long https://github.com/whatwg/html/issues/4607, but I will summarize here. rniwa@ indicated that filing an issue would be appreciated.

If you visit https://boom-bath.glitch.me/tabindex.html in Safari:

- You can tab to each <area> element in the last row, and it will become the document.activeElement.
- You can click your mouse on each <area> element in the last row, and it will become the document.activeElement.
- If you click the "click me" button in the last row, which will attempt to call .focus() on the first of the <area> elements, document.activeElement stays as the <body>.

This is a strange exception. Besides <area>, all elements that are click/sequentially focusable, are also programmatically focusable. We're contemplating (in the above-linked HTML issue tracker) making it a spec requirement, or at least recommendation. So we thought maybe Safari would like to change <area> to behave like other elements in this regard.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190610/14ed5014/attachment.html>