Open Bug 1963186 Opened 1 year ago Updated 1 year ago

Use DOM order rather than frame tree order for top-level document focus navigation.

Categories

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

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

Tracking

()

People

(Reporter: emilio, Unassigned)

References

Details

That's what the spec does. Now that we have popovers and so on, nsFocusManager::GetNextTabbableContent is kind of unwieldy. Also, it causes inconsistencies like bug 242829 (where captions inside shadow dom for example use DOM order, but outside might not be tabbable).

We might want some special cases for XUL popups perhaps, but IMHO we should move to a model much more like what the spec does.

Cc'ing some folks just to get opinions (I don't think I have the cycles to work on this right now). Would be nice if someone does tho :)

Severity: -- → S3
OS: Unspecified → All
Hardware: Unspecified → All
You need to log in before you can comment on or make changes to this bug.