Enable BrowsingContext preservation in early beta
Categories
(Core :: DOM: Content Processes, task, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox81 | --- | fixed |
People
(Reporter: pbone, Assigned: pbone)
References
Details
Attachments
(1 file)
Relman have advised that we don't need an experiment for BC Preservation at this stage. We can enable BC preservation in early beta, if it looks good in early beta we may uplift a patch to let it ride to late beta and release.
| Assignee | ||
Comment 1•5 years ago
|
||
| Assignee | ||
Comment 2•5 years ago
|
||
Note that this is mostly-unused code on mobile, so by going to beta we're also going to beta on mobile and that's okay.
We're also waiting on QA, we expect to hear from them by Friday the 21st, merge day is the 24th.
Updated•5 years ago
|
Comment 4•5 years ago
|
||
| bugherder | ||
Comment 5•5 years ago
|
||
Not sure which bug to file the regression on, feel free to move it...
After this change browser_pdfjs_saveas.js starts hanging when using a release build. The test ends up hanging on BrowserTestUtils.waitForContentEvent on a browser that loads a file uri. The event makes it back to the parent process but fails this check.
Running with fission.preserve_browsing_contexts=true the test runs fine.
| Assignee | ||
Comment 7•5 years ago
|
||
Given that we've had BC preservation in nightly for a while, and that's where a lot of testing happens. It may almost be safer to let it ride since that might be the more well tested configuration.
Description
•