Unexpected behavior of dcc.Store object containing radar information on Firefox

[lcarlaw]

Submitted this as a reference. Unaware of a quick fix. This issue is only evident in the Firefox browser. Recommendation is to run in Chrome or Safari only.

If a user initially selects 1 radar and a site to transpose to, but then selects 2 or 3 radars (for which no transposing should be possible), the previous new_radar site is still stored in the radar_info dcc.Store object.

Function transpose_radar is always called first by a change to the radar quantity or transpose radar dropdown. If the radar quantity is > 1, radar_info['new_radar'] is set to a None string. This is fine across all browsers.

When the user goes to make new radar selections via the map, function transpose_radar is executed. In Safari and Chrome sessions, radar_info['new_radar'] is correctly returned as a None string. In Firefox, this value is the previous new_radar selection, indicating that the radar_info dictionary was likely never propagated to the dcc.Store object. A visual of the differences between two browsers is below, where the first set is from Chrome, and the second on Firefox. Right after the "launch" line, a selection of 2 radars was made from the dropdown menu. The radar output is the value of new_radar at the time of the corresponding function.