Closed Bug 1580811 Opened 5 years ago Closed 4 years ago

Add support for testing fission OOP iframes in xpcshell tests

Categories

(Core :: DOM: Content Processes, task, P2)

task

Tracking

()

RESOLVED FIXED
mozilla80
Fission Milestone M6a
Tracking Status
firefox80 --- fixed

People

(Reporter: zombie, Assigned: u608768)

References

(Blocks 1 open bug)

Details

Attachments

(3 files, 1 obsolete file)

Currently the largest part of extension APIs are tested via xpcshell tests, simulating content loads via windowless browsers:

https://searchfox.org/mozilla-central/source/toolkit/components/extensions/ExtensionXPCShellUtils.jsm#175
https://searchfox.org/mozilla-central/search?q=loadContentPage&path=components%2Fextensions

Unfortunately, running that with Fission iframes currently doesn't work, since part of our process switching logic is in browser code.

We should fix this, instead of moving all our tests (back) to other, less efficient test suites like mochitest.

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Fission Milestone: --- → ?

Blocks enabling Fission in Nightly (M6)

Fission Milestone: ? → M6
Blocks: 1628307

Tracking for Fission M6a

Depends on DocumentLoadListener bug 1636169

Severity: normal → N/A
Fission Milestone: M6 → M6a
Depends on: 1636169
Priority: -- → P2
Assignee: nobody → kmadan
Depends on: 1640019
No longer depends on: 1636169

This makes it easier for callers to set LoadContext fields on the new
BrowsingContext.

Attachment #9157442 - Attachment description: Bug 1580811 - Set the correct LoadContext fields on the ContentPage browser, r?nika,zombie → Bug 1580811 - Set LoadContext fields on the ContentPage browser, r?nika,zombie
Attachment #9157441 - Attachment is obsolete: true

Originally authored by :willdurand for bug 1573456.

TODO: Mention why/how bug 1637869 fixed this.
TODO: This still fails when we run with e10s/remote?

Depends on: 1648545
No longer depends on: 1648545
Attachment #9157442 - Attachment description: Bug 1580811 - Set LoadContext fields on the ContentPage browser, r?nika,zombie → Bug 1580811 - Make the ContentPage browser work with out-of-process frames, r?nika,zombie
See Also: → 1646817
Pushed by kmadan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f9c8318e3c01
Make the ContentPage browser work with out-of-process frames, r=nika,zombie
https://hg.mozilla.org/integration/autoland/rev/d18f8e821cc7
Add xpcshell test to check that we process-switch cross-origin frames, r=zombie
https://hg.mozilla.org/integration/autoland/rev/7733de7d4f5a
Add xpcshell test to check that moz-extension: redirect by webRequest is loaded in the correct process, r=zombie

Bug 1580764 made it so we use BrowsingContext IDs rather than window IDs to compute frame IDs. The new test is still checking the window ID.

Flags: needinfo?(kmadan)
Pushed by kmadan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0bfd6bae286a
Make the ContentPage browser work with out-of-process frames, r=nika,zombie
https://hg.mozilla.org/integration/autoland/rev/85ca6cff7dfb
Add xpcshell test to check that we process-switch cross-origin frames, r=zombie
https://hg.mozilla.org/integration/autoland/rev/4e9d6619c9d5
Add xpcshell test to check that moz-extension: redirect by webRequest is loaded in the correct process, r=zombie
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: