dom/ipc/tests/browser_cancel_content_js.js fails with session history in the parent
Categories
(Core :: DOM: Navigation, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox83 | --- | fixed |
People
(Reporter: farre, Assigned: farre)
References
Details
Attachments
(2 files)
With fission and session history in the parent, it is never a blocking action to do BrowserTestUtils.loadURI when doing so would result in a remoteness change. Currently then only thing that is needed to do on the origin content process (that would block loading and trigger the content cancelling in the process hang monitor) is to flush session store state and that gets removed with session history in the parent.
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 1•4 years ago
|
||
|
|
Assignee | |
Comment 2•4 years ago
|
||
To force navigation to block on the long running script it needs to be
loading a page on the same domain as the blocking script, otherwise
fission and Session history in the parent will happily change
remoteness to another process and load immediately.
Depends on D90825
Pushed by afarre@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ff6f649014ee Part 1: Move decision to cancel to ProcessHangMonitor. r=smaug https://hg.mozilla.org/integration/autoland/rev/e4d909226e90 Part 2: Change to same domain navigation. r=smaug
|
||
Comment 4•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/ff6f649014ee
https://hg.mozilla.org/mozilla-central/rev/e4d909226e90
|
||
Updated•4 years ago
|
Description
•