Closed denisemauldin closed 6 years ago
There's a "persistence" system which works by default to maintain view-regions and a few other bits of state. Tends to make sense when using Biodalliance as a stand-alone application, less so when embedding. You'll want to use either the noPersist
or the noPersistView
option to disable this behaviour. See here for more details.
For posterity: noPersistView
only disables the browser location settings (afaict). In order to not have the browser save the track locations to localStorage you have to use noPersist
. So if you need to load either https or http tracks based on the window proto, you need to set noPersist
so it'll update the track locations.
I have a React component that loads biodalliance. I send it a new
viewRegion
and a newbed
string to update the information displayed by the component. However, after the first time, the browser no longer updates to the location and I have to call thesetLocation
API (which means that the window has to scroll/refresh twice). Why does it cache the previous location when I'm creating a new browser on load?