It looks like we have the correct data for the pinned tab within `revivedCrashedTab`, but I believe the problem is that we return early here https://searchfox.org/mozilla-central/source/browser/components/sessionstore/SessionStore.jsm#3944-3946 and don't end up entering `restoreTab`. Looking more into why `this._crashedBrowsers.has(browser.permanentKey)` would now be false after that patch.
Bug 1624511 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
It looks like we have most of the correct data for the pinned tab within `revivedCrashedTab`, but I believe the problem is that we return early here https://searchfox.org/mozilla-central/source/browser/components/sessionstore/SessionStore.jsm#3944-3946 and don't end up entering `restoreTab`. Looking more into why `this._crashedBrowsers.has(browser.permanentKey)` would now be false after that patch. It might have something to do with `aTab.linkedBrowser`
It looks like we have most of the correct data for the pinned tab within the `revivedCrashedTab` method, but I believe the problem is that we return early here https://searchfox.org/mozilla-central/source/browser/components/sessionstore/SessionStore.jsm#3944-3946 and don't end up entering `restoreTab`. Looking more into why `this._crashedBrowsers.has(browser.permanentKey)` would now be false after that patch. It might have something to do with `aTab.linkedBrowser`
It looks like we have most of the correct data for the pinned tab within the `revivedCrashedTab` method, but I believe the problem is that we return early here https://searchfox.org/mozilla-central/source/browser/components/sessionstore/SessionStore.jsm#3944-3946 and don't end up entering `restoreTab`. Looking more into why `this._crashedBrowsers.has(browser.permanentKey)` would now be false after that patch.