Enabling/Disabling Hatch in browser client causes loss of settings

Bug #1472316 reported by Bill Erickson on 2015-07-07
This bug report is a duplicate of:  Bug #1646166: Hatch 2.12 Omnibus. Edit Remove
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

Evergreen 2.8

When the browser client is used without Hatch, local settings are stored in the browser's localStorage. If a client is used for some time without Hatch, collecting localStorage data, then Hatch is later activated, existing local settings will be inaccessible, since localStorage is ignored (for most settings) once Hatch is enabled.

Similarly, when disabling Hatch, all values that were stored in Hatch will be lost to the browser, since Hatch will no longer be queried.

When activating Hatch, we are adding a data source, so we just need to agree on a strategy for querying both and/or moving/cloning data between sources.

In the case of deactivating Hatch, where we are losing a data source, we'll need a migration strategy. For example, we could show a dialog asking the user if they wish to copy the data from Hatch into the browser. Or just do it automatically.

Bill Erickson (berick) on 2015-07-07
summary: - Enabling Hatch in browser client ignores existing (in-browser) settings.
+ Enabling/Disabling Hatch in browser client causes loss of settings
Jeff Godin (jgodin) on 2016-06-03
tags: added: hatch
Kathy Lussier (klussier) wrote :

Marking as a duplicate of bug 1646166 since we now have a method of manually transferring data between the browser and hatch (in both directions.)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers