Open Bug 1580752 Opened 1 year ago Updated 13 days ago

Fire RemoteWebProgress onLocationChange for subframe location changes

Categories

(Core :: DOM: Navigation, task, P2)

task

Tracking

()

ASSIGNED
Fission Milestone M4.1

People

(Reporter: kashav, Assigned: kmag)

References

(Blocks 2 open bugs)

Details

This came up while working on bug 1578465.

We currently don't fire onLocationChange for remote subframe location changes.

No longer blocks: 1541173
Fission Milestone: --- → M4
Component: Mochitest → Document Navigation
Priority: -- → P2
Product: Testing → Core
Version: Version 3 → unspecified
No longer blocks: 1578465

I assume this will include OnContentBlockEvent too? We need that for bug 1590696.

Blocks: 1590696

This is in-turn blocking the trackingUI M-fis tests.

Fission Milestone: M4 → M4.1
Assignee: kmadan → kmaglione+bmo
No longer blocks: 1590696

Kris, are you still working on this onLocationChange bug? It's blocking some M4.1 mochitests (such as bug 1592777). Can we delegate this bug to a different Fission engineer?

Flags: needinfo?(kmaglione+bmo)

(In reply to Chris Peterson [:cpeterson] from comment #3)

Kris, are you still working on this onLocationChange bug? It's blocking some M4.1 mochitests (such as bug 1592777). Can we delegate this bug to a different Fission engineer?

Not actively. My understanding is that it's not currently blocking anything, so it hasn't been a high priority. If it is blocking something, someone will need to explain to me what and why.

Flags: needinfo?(kmaglione+bmo)

(In reply to Kris Maglione [:kmag] from comment #4)

Not actively. My understanding is that it's not currently blocking anything, so it hasn't been a high priority. If it is blocking something, someone will need to explain to me what and why.

Ethan Tseng told me (three months ago, bug 1592777 comment 3) the browser_popupNotification_3.js test (bug 1592777) was blocked waiting for this onLocationChange fix. I will confirm with MattN, triage owner for that popup test.

You need to log in before you can comment on or make changes to this bug.