It would appear that dragging the map in Google Chrome can put OpenMaps layers at the first index - which isn't intended behaviour. More debugging is necessary, but most likely html5sortable is responding with an index -1, resulting in index 0, which should remain the place of the satellite imagery layer.
It would appear that dragging the map in Google Chrome can put OpenMaps layers at the first index - which isn't intended behaviour. More debugging is necessary, but most likely html5sortable is responding with an index -1, resulting in index 0, which should remain the place of the satellite imagery layer.