-
-
Notifications
You must be signed in to change notification settings - Fork 860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] bounds set in MapOptions are sometimes ignored #1412
Comments
I can confirm this...I noticed this the other day with a report of bounds not working (preventing dragging), but sometimes would display zoom 0. Quite from my Discord:
So, originally there was a addPostFrameCallback in there, to call fitBound() after it has a correct size calculated...maybe some other code introduced as meant that this is no longer good enough, and needs further to wait. I note in Web, this works fine, and I suspect that's because typically there are more tiles to display and its a bit slower. |
It looks like it was the code from this 4276a91 which is weird, as I'm sure we tested this (but maybe we only tested it on web which does works?). So it looks like the original problem is still there or back. Cue trying to fix that, for flickering to return! |
Possible fix at #1413 please test thoroughly everyone who uses bounds, as it can be hard to replicate this problem and the initial flashing problem, as it can depend on device :) |
@ibrierley the PR seems to have fixed the issues 👍 |
Closing as merged, thanks! |
What is the bug?
If i define bounds in MapOptions these are sometimes ignored - and the map shows the full world map. If i have any interaction with the map (even with disabled interactions) the zoom seems to fix itself.
Bildschirmaufnahme.2022-12-05.um.13.40.36.mov
What is the expected behaviour?
The map is zoomed to the bounds.
How can we reproduce this issue?
Do you have a potential solution?
No response
Can you provide any other information?
Workaround is to set
Platforms Affected
MacOS
Severity
Erroneous: Prevents normal functioning and causes errors in the console
Frequency
Once: Occurred on a single occasion
Requirements
flutter doctor
finds no relevant issuesThe text was updated successfully, but these errors were encountered: