Closed Bug 1660169 Opened 4 years ago Closed 1 year ago

[Win] session restore does not display TAB-name after an about:crashparent

Categories

(Firefox :: Session Restore, defect)

Firefox 81
Unspecified
Windows 10
defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox81 --- fix-optional

People

(Reporter: cfogel, Unassigned)

Details

(Keywords: regression, regressionwindow-wanted)

Attachments

(2 files)

Affected versions

  • 81.0a1 (2020-08-19)

Affected platforms

  • Windows 10

Steps to reproduce

  1. Launch Firefox, open several tabs, wait for pages to load;
  2. In the second one type about:crashparent;
  3. Restart the browser(yes& input test on details);

Expected result

  • browser and session restored;

Actual result

  • tabs restored but with [New Tab] instead of name+favicon

Regression range

  • will check and provide one asap;

Additional notes

  • attached screenshot with the issue, opened tabs were the ones in the top-sites section;
  • the pages do load content and update name+favicon after being accessed;
  • S3 as suggested severity, since it might be limited to about:crashparent test.
Has Regression Range: --- → no
Has STR: --- → yes
Summary: [Win] sesssion restore does not display TAB-name after an about:crashparent → [Win] session restore does not display TAB-name after an about:crashparent

Hi Mike, can we assume this to have a low severity for end users? Thank you!

Flags: needinfo?(mdeboer)
Severity: -- → S4
Flags: needinfo?(mdeboer)

Hi,
I downloaded nightly 80.0a1 (2020-07-19) (64-bit), 81.0a1 (2020-08-01) , 82.0a1 (2020-08-27) (64-bit), but I'm unable to reproduce. I don't think we can perform mozregression right? Since when crashing browser, the mozilla crash reporter window won't be triggered so session won't be restored.

The steps I followed: I checked "Restore previous session" in about:preferences, opened youtube, wikipedia, facebook and reddit from top sites (new tab), In the second tab I typed about:crashparent; when restoring session, tabs are correctly displayed.

let me know if I can help in any other way.
Best,
Clara

Flags: needinfo?(cristian.fogel)
QA Whiteboard: [qa-regression-triage]

Hi @Clara,
Indeed, using mozregression is not an option and the only way would be to check manually.
Due to the low impact and use-case of this issue would rather invest time in other issues.

One more addition on my side, is that the re-open tabs for the issue was done via CTRL+Shift+T as well and led to the same result at that date.

Flags: needinfo?(cristian.fogel)
Attached video restore(1).webm

Hi,

Can you let me know if I'm missing any steps? Ctrl Shift T just opens last closed tab, so Im still unable to reproduce.
Best,

Clar

Flags: needinfo?(cristian.fogel)

Nope, that's pretty much it.
Probably missing some other dependency or it might have been a one-off; since with 82.0a1 (2020-09-01) and a fresh profile I cannot reproduce the issue anymore either.

Flags: needinfo?(cristian.fogel)

If this is still an issue, please reopen.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: