Closed Bug 1574543 Opened 5 years ago Closed 5 years ago

Add and use a Fission-compatible utility method to check if a remote type is for web content

Categories

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

task

Tracking

()

RESOLVED FIXED
mozilla70
Fission Milestone M4
Tracking Status
firefox70 --- fixed

People

(Reporter: mccr8, Assigned: mccr8)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

There are at least a couple of tests, namely browser_new_file_whitelisted_http_tab.js and browser_navigation_process_swap.js, that check if the remote type is equal to E10sUtils.WEB_REMOTE_TYPE to decide if the remote type is for a content process. With Fission, the remote type will instead start with webIsolated=.

Summary: Add and use a Fission-compatible utility method for check if a remote type is for web content → Add and use a Fission-compatible utility method to check if a remote type is for web content

Some tests check that the remote type is "web", but with Fission it
will instead start with "webIsolated=".

I fixed some of the errors in
browser_new_web_tab_in_file_process_pref.js and
browser_httpResponseProcessSelection.js, but there are other failures,
so they remain disabled.

To find these tests, I looked at the places that use E10SUtils.WEB_REMOTE_TYPE.

Pushed by amccreight@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d70f2cf4811f
Add and use a Fission-compatible utility method to check if a remote type is for web content. r=mconley
Fission Milestone: --- → M4
Status: NEW → ASSIGNED
Priority: -- → P2
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: