Skip to content

Release Notes : v0.2.6

Date: 25th July 2026

Summary

This release introduces a reusable modal component and a login modal that guides unauthenticated users toward signing in when they try to save or import routes, adds a prominent login button to the sidenav for guests, switches sliding panels to solid colours for improved focus and readability, fully aligns modal and auth styles with the design-token system, and fixes coordinate handling so WGS84 (Lat, Lon) inputs work correctly for routing.

What Changed

Reusable Modal Component & Authentication UX

  • Extracted the point-delete confirmation dialog styles from map.css into a new shared components/modal.css, renaming classes to generic modal-* names so the same component can be reused for future dialogs (login, delete route, etc.).
  • Added an authentication-wall / login modal that appears when a guest user attempts to save a route, view saved routes, or import a route, replacing the previous tooltips.
  • Hid the “Delete Account” and “Log Out” options in the settings panel for unauthenticated users to reduce visual clutter.
  • Added a clear login button at the bottom of the sliding navigation bar that is only shown to guests, giving them an obvious path to the login page without needing to know the URL.

Sliding Panel Design

  • Replaced the glassmorphism (translucent) backgrounds of the Import Route, Saved Routes and Settings sliding panels with solid colours driven by design tokens.
  • The change improves content focus, reduces visual distraction from the map behind the panels, and automatically adapts to light/dark theme.

CSS Consistency & Theming

  • Updated modal.css and auth.css to use design tokens from tokens.css instead of hardcoded colours and redundant html.dark rules.
  • Added new token values needed by the solid-panel redesign and the modal component, ensuring consistent theming and easier future maintenance.

Bug Fixes & Reliability

  • Fixed routing so that users can enter WGS84 (latitude/longitude) coordinates without receiving false “outside Cumbria” errors.
  • Added an isLonLat() utility that detects whether coordinates are already in Lat/Lon form and skips the unnecessary Web-Mercator conversion.
  • Corrected corresponding backend conversion and a naming bug that previously prevented route creation even after the Cumbria check was resolved.