sync-about-blank causes an unexpected, additional about:blank in session store
Categories
(Core :: Session Restore, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox146 | --- | unaffected |
| firefox147 | --- | unaffected |
| firefox148 | --- | fix-optional |
People
(Reporter: vhilla, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
2.20 KB,
text/plain
|
Details |
Testcase
add_task(async function () {
const tab = await BrowserTestUtils.openNewForegroundTab({ gBrowser, opening: "https://example.com", waitForLoad: true });
await TabStateFlusher.flushWindow(window);
let state = SessionStore.getCurrentState(true);
SessionStore.keepOnlyWorthSavingTabs(state);
dump(JSON.stringify(state) + "\n");
});
Expected: state should list one window with one tab for example.com
Actual: state contains one window with two tabs about:blank and example.com
| Reporter | ||
Comment 1•10 months ago
|
||
I'm unsure if this is observable outside of browser tests.
| Reporter | ||
Updated•10 months ago
|
Comment 2•10 months ago
|
||
Set release status flags based on info from the regressing bug 543435
| Reporter | ||
Comment 4•10 months ago
|
||
Yes, maybe even S4.
I wasn't able to trigger this directly in the browser and am not aware of bugs being filed for about:blank being restored unexpectedly. As long as this only happens with BrowserTestUtils, it seems ok.
Comment 5•10 months ago
|
||
Next week is the final week of nightly for Fx148.
:vhilla, what is the current status of the investigation/priority here? Is this something you need to fix for Fx148?
| Reporter | ||
Comment 6•10 months ago
|
||
As long as we don't see this happening in the wild, i.e. it only occurs with BrowserTestUtils, this is low priority.
Updated•10 months ago
|
Description
•