Travis Leithead

The linked issue is now closed. Closing this one.

Current plan: * Add default handing for 'Home' and 'End' keys to move to the beginning/end of the set of focusgroup candidates.

Regarding https://github.com/openui/open-ui/issues/573#issuecomment-1278898701, it seems odd to me that VO would automatically switch from a pseudo-Tab based control navigation to an pseudo-Arrow key navigation for radio buttons, but alas, this must...

Current plan: * Consider closing, unless new information surfaces?

Looking again at adding a memory (and making it the default behavior): I do like the simplicity of the "memory-override" approach outlined above where the platform hijacks all the focusable...

I'd like to propose a 4th approach, not mentioned above, that is similar to the current approach of not having a memory (and respecting all tabindex values), but which does...

Note: @gfellerph proposed an alternative approach that sticks with "memory-override", but addresses the problem of getting trapped in the input element by allowing the platform to temporarily make the next/previous...

Need to also figure out under what conditions the memory of the focusgroup will be forgotten. * @aleventhal [mentions](https://github.com/openui/open-ui/issues/537#issuecomment-1139021993) that one case is when the focusgroup element is hidden. *...

@gfellerph thanks for illustrating your idea with examples. > @travisleithead, is the difference between "memory-override" and "entrance-memory" that tabindex settings by the author are respected the first time a focusgroup...

Current plan: * change the explainer to add a "memory" to the focusgroup with the least disruption/magic to existing Tab behavior as possible. A roving-tab-index "memory" is a nearly universal...