You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if i set the maxBounds the zoom would be also fixed. But it would be nice if it depends on the window size, so that its possible to see full bounds on max zoom out.
here i see full frame on max zoom out
here i dont see full frame on max zoom out
There is olso a problem with flyto by using maxBounds. It flicker - i think because of flying out and in of boundary.
The text was updated successfully, but these errors were encountered:
Hi @strech345 ,
Thank you for submitting your issue. Could you please use the provided issue template for this issue? It includes spaces for key information like the version of mapbox-gl-js that you're using and exact steps to reproduce the issue. Because these are missing from your report, we cannot diagnose and fix the issue.
maxBounds is meant to constrain the viewable area of the map by preventing the user from zooming / panning outside those bounds. if its behaving unexpectedly we'd like to help but need the information requested in the template 👍
I think the original report was about changing the maxBounds behavior so that you can zoom out further than maxBounds dictates so that you can see the maxBounds area fully. No plans to implement this currently. And the flyTo flickering issue is likely #2521.
if i set the maxBounds the zoom would be also fixed. But it would be nice if it depends on the window size, so that its possible to see full bounds on max zoom out.
here i see full frame on max zoom out
here i dont see full frame on max zoom out
There is olso a problem with flyto by using maxBounds. It flicker - i think because of flying out and in of boundary.
The text was updated successfully, but these errors were encountered: