Travis Leithead

A digest of the CG discussion above: * I thought focusgroup did single tab stop/roving tab index--you're saying it doesn't/confusing for page navigations? (@mfreed7, @dbaron, @scottaohara) * See https://docs.google.com/document/d/1cOxjjZdvFfpexiN1x-MpNJLXrmbrR0xp1sRCTbaQ29c/ for...

@kbrilla that makes sense. I'll add this note to issue #537 and think about what the opt-out will look like.

@lgarron I'm looking into this right now. Feel free to ping-me offline for questions in the meantime...

@wseltzer, @siusin, to close the loop on this: Microsoft has no concerns with @lgarron's individual contribution here--it is approved for him to make this contribution as an individual. @siusin please...

After reading through [Invokers](https://open-ui.org/components/invokers.explainer/) and [Interest Invokers](https://open-ui.org/components/interest-invokers.explainer/), it made me think of having a very simple attribute that just translates "interest" (e.g., via focus) into a "toggle" or "click" on...

Current plan: * Update the explainer such that CSS Toggles is not a proposed solution to the selection part of a focus+selection composed control.

PR #1021 has updated the CSS Toggles references. Closing this now.

And after noodling more on this, I think that we need to revisit the notion that the element that declares a focusgroup does not participate in it. > ⭐ Note:...

I've been looking at real-world use cases for when "Part 4" above might be useful (the "orthogonal" use-case), and in nearly every scenario I've found (menus, toolbars, tabs, etc. [combing...

Yes, I think a focusgroup could help make this navigation easier, but it would need to be modeled with the right pattern. (Of course, I'd like to see a focusgroup...