Fix browser_unknownContentType_title.js to pass in Fission (ie cross-origin downloads wipe the content window and content window title in Fission)
Categories
(Core :: DOM: Navigation, defect, P1)
Tracking
()
People
(Reporter: Gijs, Unassigned)
References
Details
This test fails because the download that it triggers happens in a different content process from the page that's loaded before it, so the page title in gBrowser.contentTitle
is correctly updated when we clear out that docshell and replace it with one in the different process.
In order to fix this, we need to ensure that loadURI
calls that happen to trip a download rather than targeting a docshell actually take place in the parent, so fixing this test is blocked on bug 1574372.
Updated•1 year ago
|
Comment 1•1 year ago
|
||
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
Updated•1 year ago
|
Comment 2•1 year ago
|
||
I have working patches for bug 1574372, which still don't fix this, due to bug 1601779.
Comment 3•1 year ago
|
||
(In reply to Matt Woodrow (:mattwoodrow) from comment #2)
I have working patches for bug 1574372, which still don't fix this, due to bug 1601779.
Seems like the fix won't be in the test itself nor in Tabbed Browser code. Moving this to Core::DOM: Navigation to match bug 1601779.
The priority flag is not set for this bug.
:kmag, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 5•1 year ago
|
||
P1 for Fission mochitest failure (M4.1)
Updated•1 year ago
|
Description
•