Skip to content

Focus navigation is broken if trigger is a descendant of popover #12873

Description

@ltenmoz

What is the issue with the HTML Standard?

Currently associated-focus-navigation-owner has the step:

  1. If element is in the popover showing state and has a popover trigger set, then return element's popover trigger.

However, the trigger can be the popover or a (focus scope) descendant of it. This leads to the flattened tabindex-ordered focus navigation scope being an infinite list, which is perhaps not ideal.

It's not clear how focus navigation should behave in those cases. Maybe we can add some language about skipping item if item = owner in the flattened tabindex-ordered focus navigation scope algorithm?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions