Re: [w3c/webcomponents] default focus: Update for the "hint" approach (#852)

tkent-google commented on this pull request.



> @@ -36,13 +37,24 @@ class MyButton extends HTMLElement {
 
 ## Proposal
 
-Add a new property `matchFocusBehaviorOf` to `ElementInternals`, which accepts a string containing a tagname and optionally an attribute with a value (so it will accept values like `div`, `a[href]`, `input[type='checkbox']` , but not `.class`, `*`, etc.). The custom element will then be treated as if it has that tagname and attribute in terms of focus.
+Add `focusBehavior` property to `ElementInternals`, which accepts one of three string values; `"none"`, `"focusable"`, and `"infer"`.
+`"none"` indicates the element is not focusable, and `"focusable"` indicates the element's focus behaivor is same as `<div tabindex=non-negative-value>`. `"infer"` indicates the element is focusable, however a user-agent decides click behaivor and TAB behavior with hints from the element.

I thought programatically-focusable was always true for `"focusable"` and `"infer"`.  The last sentence should mention programatically-focusable if such a built-in element exists.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/pull/852#discussion_r343462878