Open scottaohara opened 2 years ago
For "first tabbable" I am planning on using the "sequentially focusable" term in the HTML spec because it seems to refer to things you can focus to by pressing tab: https://html.spec.whatwg.org/C/#sequentially-focusable
Seems fine for now, but could sequentially focusable become confusing after focusgroup becomes part of the spec?
On Tue, Jun 7, 2022, 6:08 PM Joey Arhar @.***> wrote:
For "first tabbable" I am planning on using the "sequentially focusable" term in the HTML spec because it seems to refer to things you can focus to by pressing tab: https://html.spec.whatwg.org/C/#sequentially-focusable
— Reply to this email directly, view it on GitHub https://github.com/whatwg/html/issues/7710#issuecomment-1149222178, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKQAZUHPOFX2QOBHBVCTBLVN7B6TANCNFSM5QZYEWRA . You are receiving this because you were mentioned.Message ID: @.***>
Regarding the question of which issues in https://github.com/whatwg/html/pull/4184#issuecomment-1072536425 should be considered blocking for writing up a spec of https://github.com/whatwg/html/wiki/dialog--initial-focus,-a-proposal#initial-dialog-focus-logic : "sequentially focusable" is the correct spec term here. This issue should be unblocked.
I don't believe the introduction of focusgroup (in whatever form it ends up) will change how appropriate the term sequentially focusable is, but maybe I'm missing something.
Do we think that "sequentially focusable" will become a confusing term once focusgroup is introduced? The items in a focusgroup are still sequentially focusable, but with the up/down arrow keys. Apologies for the bikeshedding :) Since "tabbable" is too device-specific, perhaps "in the primary focus cycle" ?.
I don't really see the confusion? They're still focusable in sequence, so the term "sequentially focusable" seems fine. Perhaps you could give an example of the code you think will be confusing?
Also, this is all very speculative, focusgroup is a proposal which hasn't been sent to the WHATWG yet, and I anticipate we can have the discussion of what to call focusgroup's terms when it is?
Per the dialog initial focus proposal, there was a lot of discussion in the orginal Google doc about the use of
The reason for this is because of the user setting on macOS where not all elements that would otherwise be tabbable are by default. The following are just a few key instances of comments made in that thread to allow the conversation to continue here as necessary:
@westbrook
@cookiecrook
@aleventhal
@scottohara
@cookiecrook
Further discussion needs to occur on alignment with Gecko, Webkit and Chromium on allowing scrollable containers to receive keyboard focus. This being particularly important when there is no focusable elements within a scrollable container (e.g.,
<div style="overflow: auto; max-height: 300px>lots of static text</div>
").