openui
[focusgroup] Is focusgroup the right name?
@benbeaudry brought this up in a discussion today when going over the explainer. Focus group already has a definition, and even a Wikipedia page:
A focus group is a group interview involving a small number (sometimes up to twelve) of demographically predefined participants.
We should consider other names that may more accurately represent the behavior, and if one can be found, rename.
I like the name focusgroup, but if the name collision is a problem, maybe focusscope?
I'm not against the name per say; just want to make sure it's not something we come to regret in the future.
Confusion aside with the other meaning of a focus group, I wonder if the name isn't too vague as it is. For example, an other attribute used to control focus in a web page is called tabindex, scoping the intent to the tab key directly from the name (note: tabindex is a bad name/design imo; it's just to set the focusable state, and control the focus order, something that causes a ton of accessibility issue when done the wrong way. The thing I like about this attribute its name indicates that it meant to work only with the tab key).
Just brainstorming here, but given that the focusgroup attribute is meant to create arrow-keys navigation scoped to a specific component, what about something along the lines of arrow-navigation or arrow-focusgroup or something like that?
My main concern about the name being generic to "scoped focus in a particular component" is that we might want to create new attributes/solutions in the future wrt to keyboard navigation that are also essentially enabling a "scoped focus in a particular component" scenario.
I'm fine with focusgroup, but we should be prepared for future awkwardness if arrow-keys aren’t the only scenario that allows managing focus in a component.
Because it's built-in it will have to be a non hyphenated name per current guidelines fwiw.
I don't think the name is too important right now something we can definitely discuss down the line.
Fwiw I think focusgroup is better than focusscope because it's grouping focus into a single tab stop.
It's worth noting that, if I understand correctly, ARIA refers to this as a "composite". See https://w3c.github.io/aria/#composite and https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#keyboardnavigationinsidecomponents. But maybe you're trying to avoid assigning semantics to this attribute, keeping it purely in the realm of behavior?
