Closed Bug 1646488 Opened 4 years ago Closed 4 years ago

Figure out what to do for autofocus in cross-origin iframe

Categories

(Core :: DOM: Core & HTML, task)

task

Tracking

()

RESOLVED INVALID
Fission Milestone MVP

People

(Reporter: kmag, Unassigned)

References

(Blocks 2 open bugs)

Details

It isn't Fission-compatible, and isn't likely to work with autofocus elements in OOP frames.

Blocks: fission
Severity: -- → N/A
Type: defect → task

Do we actually allow autofocus in cross-origin iframes? How much do we care?

Tracking for Fission M7 Beta until we decide whether this needs to block shipping Fission.

Fission Milestone: --- → M7

Henri, is this critical for blocking Fission Nightly or Fission Beta?

Flags: needinfo?(hsivonen)

I don't have actual evidence of use cases, but my guess is that this isn't critical or blocking (in fact, I think explicitly not allowing this might be a valid outcome).

Flags: needinfo?(hsivonen)

The issue is in GetInProcessTop usage in TriggerAutoFocus and nsAutoFocusEvent. Henri said this isn't disastrous and can be dealt with later so moving to MVP.

Fission Milestone: M7 → MVP
Summary: Fix GetInProcessTop usage in TriggerAutoFocus and nsAutoFocusEvent → Figure out what to do for autofocus in cross-origin iframe

I think this is INVALID/WONTFIX, we already don't trigger autofocus for cross-origin iframes even without fission: https://searchfox.org/mozilla-central/rev/919f7400e2e12bc963ee2ae8400ef961972c3059/dom/base/BindContext.cpp#24

But please reopen if I somehow got that wrong.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.