@autobusal/routes-order 1.33.9 → 1.33.10

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 1.33.10 (2026-08-29)
+
+- The return date falls back to the outbound when the URL carries no real one ('none' on a one-way link), so switching a collapsed search to Round Trip opens the calendar on the month being travelled and cannot offer a day before the departure.
+- The collapsed search panel sits above the step markers: its backdrop-filter creates a stacking context, so the date picker used to draw underneath them.
+
 ## 1.33.9 (2026-08-28)
 
 - Return-leg empty state fetches RETURN alternatives (swapped pair + return date) and its suggested-day links fill the return slot instead of rewriting the departure; nearby-city swaps map back to the URL's outbound pair (sweep #50).

package/Step1/prepare.ts

@@ -1,5 +1,5 @@
 import { Params } from 'react-router-dom';
-import { futureDate } from '@autobusal/utilities';
+import { futureDate, isPreparedDate } from '@autobusal/utilities';
 import { RoutesSearchForm } from '@autobusal/routes-search/types';
 
 const prepare = (
@@ -18,7 +18,26 @@ const prepare = (
   const to = params.to ?? defaultLocations.to;
 
   const departure = params.departure?.replace(/-/g, '/') ?? futureDate(1);
-  const _return = params._return?.replace(/-/g, '/') ?? futureDate(2);
+
+  /*
+   * Edited: Claude - Date: 2026-08-29
+   *
+   * THE RETURN DATE IS TIED TO THE OUTBOUND. A one-way URL carries the
+   * literal "none" in the return slot, and `??` only catches null - so
+   * "none" travelled all the way into the picker, whose grid is built by
+   * splitting on "/" and feeding Date.UTC: an Invalid Date, rendered as
+   * January. Switching a collapsed search from One Way to Round Trip
+   * showed exactly that.
+   *
+   * Anything that is not a real date falls back to the departure, which is
+   * also the picker's floor - so the return calendar opens on the month
+   * being travelled and cannot offer a day before the outbound.
+   */
+  const requested = params._return?.replace(/-/g, '/');
+
+  const _return = isPreparedDate(requested)
+    ? String(requested)
+    : (isPreparedDate(departure) ? departure : futureDate(2));
 
   const adults = params.adults ?? 1;
   const children = params.children ?? 0;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@autobusal/routes-order",
-  "version": "1.33.9",
+  "version": "1.33.10",
   "author": "Ferjolt Ozuni",
   "type": "module",
   "main": "index.ts"

package/styles.ts

@@ -94,6 +94,19 @@ export const SearchPanel = styled.div<{ $open: boolean }>`
   display: ${ props => props.$open ? 'block' : 'none' };
   margin-top: 14px;
   padding: 20px;
+
+  /**
+   * Edited: Claude - Date: 2026-08-29
+   *
+   * ABOVE THE STEPS, because backdrop-filter below creates a stacking
+   * context: everything inside this panel is confined to it, so the date
+   * picker's own z-index (100) could never beat the step markers sitting
+   * at z-index 1 in the page's context. Opening the collapsed search and
+   * clicking a date drew the calendar UNDERNEATH the 1-2-3-4 circles.
+   * Raising the panel itself lifts its whole subtree with it.
+   */
+  position: relative;
+  z-index: 20;
   background: ${ props => props.theme.header.transparent };
   backdrop-filter: blur(25px);
   -webkit-backdrop-filter: blur(25px);