Avoid remoteness change in browser_page_frameNavigated* tests in order to enable tests on Fission
Categories
(Remote Protocol :: CDP, defect, P1)
Tracking
(Fission Milestone:M4)
Fission Milestone | M4 |
People
(Reporter: ato, Assigned: ato)
References
Details
Attachments
(1 file)
There is an overview in the Fission mochitest spreadsheet of
Fission-only failing tests. As I outlined in bug 1585464 comment
#2 most of the remote tests pass under Fission and can be enabled
without any changes.
The browser_page_frameNavigated.js and
browser_page_frameNavigated_iframe.js tests make use of the
http://example.com/ test resource server which causes a content
browser remoteness change on navigation. We can work around this
issue and enable the tests by ensuring those test resources are
also loaded using Data URLs, using the helper I introduced in bug
1563533.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
In order to get the browser_page_frameNavigated.js and
browser_page_frameNavigated_iframe.js tests passing under Fission
we can load the test resources from the same site origin as the
initial test document. This avoids a content browser remoteness
change, which strictly speaking is not what the tests are testing.
Comment 3•5 years ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Comment 5•5 years ago
|
||
Retroactively moving fixed bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to an appropriate Fission 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
Updated•4 years ago
|
Description
•