Open Bug 1796225 Opened 3 years ago Updated 3 years ago

AutoSave: Trigger save when new engine state is pushed

Categories

(Firefox for Android :: Tabs, task)

All
Android
task

Tracking

()

People

(Reporter: gl, Unassigned)

Details

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

Currently AutoSave supports multiple triggers: Periodically, Backgrounding and Session changes. Nowadays GeckoView pushes a new state for a GeckoSession to us (instead of us asking for a snapshot). Whenever this happens we should consider this a trigger for AutoSave and save the state to disk (with some throttling) so that we do not risk loosing the new state. Otherwise we may need to wait until the next periodically trigger saves it - and by default that can take up to 30 seconds.

┆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: -- → N/A
Type: defect → task
Flags: needinfo?(cpeterson)
You need to log in before you can comment on or make changes to this bug.