Open Bug 1793186 Opened 3 years ago Updated 2 years ago

SessionStorage: BrowserState with selected tab id for tab that doesn't exist

Categories

(Firefox for Android :: General, defect)

All
Android
defect

Tracking

()

People

(Reporter: csadilek, Unassigned)

Details

From github: https://github.com/mozilla-mobile/android-components/issues/8417.

We switched from saving a SessionManager.Snapshot to a BrowserState in #7867 / 9e60a62119e4d0cb352642940faaec9da00fe1e1.

We now see the "selected tab" check fail. As a workaround I'll write a patch that clears the selected tab id in the state we are writing to disk, in that situation.

Nevertheless we should investigate how we end up in such a situation. Our reducer definitely doesn't do any checks when setting the selected tab id. But maybe this is intentional for "out of order" actions? Let's find out.

https://sentry.prod.mozaws.net/operations/firefox-beta/issues/9527493

        if (state.normalTabs.isEmpty()) {
            clear()
            return true
        }

        if (state.selectedTabId != null) {
            requireNotNull(state.selectedTab) {
                "Selected session must exist"
            }
        }

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)
Severity: -- → S3
Flags: needinfo?(cpeterson)
You need to log in before you can comment on or make changes to this bug.