* Instead of keeping the EngineSessionState inside EngineSession, we now always attach it to EngineState and also do not clear it anymore. * If the content process gets killed we now just suspend affected EngineSession instances. They will automatically and lazily get restored from the last EngineSessionState once needed. * On a content process crash we now mark the EngineState as crashed and suspend the EngineSession. We will not restore the EngineSession until explicitly restored by the application.
Android Components > Browser > State
🔴 Note: This is an experimental component still under development. APIs may change at any time. It's not recommended to directly use this component in products yet.
The browser-state component is responsible for maintaining the centralized state of a browser engine.
The immutable BrowserState can be accessed and observed via the BrowserStore. Apps and other components can dispatch Actions on the store in order to trigger the creation of a new BrowserState.
Patterns and concepts this component uses are heavily inspired by Redux. Therefore the Redux documentation is an excellent resource for learning about some of those concepts.
Usage
Setting up the dependency
Use Gradle to download the library from maven.mozilla.org (Setup repository):
implementation "org.mozilla.components:browser-state:{latest-version}
License
This Source Code Form is subject to the terms of the Mozilla Public
License, v. 2.0. If a copy of the MPL was not distributed with this
file, You can obtain one at http://mozilla.org/MPL/2.0/