The device has a location as shown in the device panel however the map shows a different location.
Firefox 147 also Chromium
The device has a location as shown in the device panel however the map shows a different location.
Firefox 147 also Chromium
<!-- github-sync-id:3945019433 -->
Root cause: hardcoded coordinates (52.5, 6.0) used as both the initial map centre and the fallback when the device has no GPS fix. These numbers were scattered across two files (map_panel.py and route_page.py) with no single point of configuration.
Changes:
Added DEFAULT_MAP_CENTER and DEFAULT_MAP_ZOOM constants to config.py
map_panel.py — initial Leaflet centre now uses config constants
Fixed in v1.9.2.
Root cause: hardcoded coordinates (52.5, 6.0) used as both the initial map centre and the fallback when the device has no GPS fix. These numbers were scattered across two files (map_panel.py and route_page.py) with no single point of configuration.
Changes:
- Added DEFAULT_MAP_CENTER and DEFAULT_MAP_ZOOM constants to config.py
- map_panel.py — initial Leaflet centre now uses config constants
<!-- github-comment-id:3908753342 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The device has a location as shown in the device panel however the map shows a different location.
Firefox 147 also Chromium
Fixed in v1.9.2.
Root cause: hardcoded coordinates (52.5, 6.0) used as both the initial map centre and the fallback when the device has no GPS fix. These numbers were scattered across two files (map_panel.py and route_page.py) with no single point of configuration.
Changes: