Exempt about:*pages from new bfcache, with the exception of about:blank
Categories
(Core :: DOM: Navigation, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox90 | --- | fixed |
People
(Reporter: neha, Assigned: annyG)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
browser/base/content/test/tabs/browser_navigate_through_urls_origin_attributes.js is failing for Fission+BFCache with an unexpected XULFrameLoaderCreated.
Anny, can you debug this failure please?
|
Reporter | |
Updated•4 years ago
|
|
|
Reporter | |
Updated•4 years ago
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 1•4 years ago
|
||
browser/base/content/test/tabs/browser_navigate_through_urls_origin_attributes.js fails with bfcache + fission because it expected that XULFrameLoaderCreated event would be not fired from the point when we open a new tab in a private window to when we navigate it to about:blank. However, initial about:privatebrowsing tab gets bfcached when we navigate to about:blank, and thus we have to create a new frame loader for the about:blank page.
To keep the memory usage down, we can exempt about:* pages (with the exception of about:blank and about:reader) from bfcache.
|
|
Reporter | |
Updated•4 years ago
|
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 2•4 years ago
|
||
This also fixes test
browser/base/content/test/tabs/browser_navigate_through_urls_origin_attributes.js
which was failing for fission + bfcacheInParent, because about:privatebrowsing
was getting bfcached, and an extra XULFrameLoaderCreated event was firing, when
we were not expecting it.
|
||
Updated•4 years ago
|
|
||
Comment 4•4 years ago
|
||
| bugherder | ||
Description
•