Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[focusgroup] Restrict usage of focusgroup on certain elements #1007

Open
travisleithead opened this issue Feb 27, 2024 · 3 comments
Open

[focusgroup] Restrict usage of focusgroup on certain elements #1007

travisleithead opened this issue Feb 27, 2024 · 3 comments

Comments

@travisleithead
Copy link
Collaborator

Forked from discussions on issue #990:

Probably worth restricting focusgroup application to certain nodes (@keithamus, @lukewarlow, @scottaohara) -- e.g., not or

This issue can track the discussion on which elements should not have focusgroup apply because no users should/will expect focusgroup behavior on such elements. See also, the related issue of how focusgroup behavior should (if at all) apply to elements that already have built-in focusgroup-like behavior #995.

The original concern is that placing a focusgroup on elements that aren't typically used for building UI widgets or that wouldn't have a role associated with a UI widget could be harmful for the accessibility of the web.

At present, both

  • <html>
  • <body>
    and probably
  • <head>

Are among the restricted elements candidates.

@lukewarlow
Copy link
Collaborator

Dialog doesn't allow tabindex and I suspect should also not allow focusgroup

@travisleithead
Copy link
Collaborator Author

The spec's updated now, following PR #1021, but there's still an open question in there about restrictions. I looked at the Shadow DOM attachShadow restrictions, and I think its a bit too restrictive for focusgroup use cases--given that <table> is excluded...

Copy link

There hasn't been any discussion on this issue for a while, so we're marking it as stale. If you choose to kick off the discussion again, we'll remove the 'stale' label.

@github-actions github-actions bot added the stale label Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants