cookie state should be keyed to the dataset id

[rbuels]

Should also switch to storing things in localStorage, since it's well supported. See http://caniuse.com/#search=localstorage

On 01/07/2014 04:30 PM, Richard Hayes wrote:

I think this might be part of a larger issue with multi-dataset
installations, where the cookie storage of selected tracks appears to be
a global value. I've seen other cases where:

1. I turn on TrackA in SpeciesX
2. I switch to SpeciesY from the datasource dorp down menu. SpeciesY
   doesn't have TrackA.
3. I switch back to SpeciesX, but TrackA is no longer selected.

[rbuels]

Approach for this would probably be to modify the cookie method in JBrowse/Browser.js to use localStorage for this instead of cookies, and to append the value returned by this.config.dataset_id to the key, if it is defined.

[Kevin-Mohamed]

i searched through JBrowse, cookie seems to be used throughout (should I replace references in the other files?)
right now replacing "tracks" with "tracks-"+this.config.dataset_id (when calling from and saving the stored tracks) in the existing cookie method seems to work

[rbuels]

No, you should modify only the cookie method in Browser.js.