Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found that map control wasn't working after the initial map load with peers. The map view would be set to a bounding box around my peers but would then become unresponsive. The buttons in the top right of the map (zoom in/out, bound) would not work.
This was an issue as I'd enabled MQTT while initially testing my node (showing me global peers) but I wanted to zoom in on my own area after disabling it later, which I couldn't do. I adjusted this initial behaviour to occur once, which then allows the user to interact with the map as expected.
I also adjusted the default "peerless" map location to be zoomed out and central-ish on the map in use, rather than zoomed into Melbourne. There's probably a better solution for this, but for now starting at a high zoom level feels more natural than a specific city - happy to revert this out if you'd prefer to keep things as is.