Ian
Ian
Interestingly enough, prior to the last couple of changes, you could kind of do this (as dragMarkers point internally was the same, however, this caused a problem where if you...
You could just add a check not to call fitBounds if you don't actually have any bounds....but ideally yes, there could be a protection /default behaviour in there (or simply...
Can you provide some example settings (with latlngs etc) to reproduce the problem.
i.e a minimal test example page that people can run that is.
Does it work with the fix (i.e latest Github release)?
Maybe put some code up, it may depends if you are using other bounds parameters like maxBounds etc as well.
I haven't tested this yet, but think this has been raised before and don't think there's any code to deal with it yet, so I think makes sense it wouldn't...
Darn I suspect this one is going to be a bit of a pain, as it may be a timing issue. The problem is, it doesn't work if its not...
I suspect this may end up being a problem we've seen before, where an initial draw doesn't know it's size on first frame (for bound calculations), and it can depend...
I don't think that would quite work, as it would be calling a move (from fitBounds) within a build. However, what if we git rid of of the initState move/fitBounds...