randy
f0ac8ac5d4
The browser-geolocation fallback was reusing GnssControl's green .gnss-marker for its own position dot -- on a machine with no real GPS chip, wifi/IP-estimated location can jump around noticeably between watchPosition updates, and a green dot doing that reads as "GNSS is somehow still being used" even when it very much isn't (confirmed: code review found no path from locate.js to /api/gnss/position at all, and GNSS was off in the report). Switched to MapLibre's own blue pulsing .maplibregl-user-location-dot -- the same look GeolocateControl itself had here before, and now visually distinct from GNSS's green on purpose rather than by accident. Verified: both markers rendered side by side (GNSS on via the simulator, plus a manually-placed browser-fallback-style marker) -- clearly different colors, no shared styling.