Open Bug 1955857 Opened 1 month ago Updated 1 month ago

Make the scope concept for sequential focus handling also take popovers into account

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

Product:
Core
Component:
DOM: UI Events & Focus Handling
Type:
defect

Tracking

()

People

(Reporter: edgar, Unassigned)

References

(Blocks 1 open bug)

Details

There is a focus navigation scope owner concept in the spec, https://html.spec.whatwg.org/#focus-navigation-scope-owner.
Our nsFocusManager also has the similar concept, but it only handle the shadow DOM. The popover is handled separately. I think it makes sense to make our scope concept in nsFocusManager also take popover into account, so that we don't need to handle them separately, and also make our code more align with the spec.

Blocks: popover
See Also: → 1949678

Hmm, besides bug 1949678, I think we generally don't handle tabindex correctly for popover. For example, https://codepen.io/edgarchen-the-decoder/pen/zxYaEZJ, when focus move out of popover, we should use the tabindex of scope owner (popover invoker) and check the ancestor scope to find the next focusable element.

Severity: -- → S3
Type: enhancement → defect
You need to log in before you can comment on or make changes to this bug.