/* ============================================================================ OVERCROSS - the tour page's one action under the thumb. Characteristic 9 of docs/design/mobile-concept.md: a thin bottom bar holding price plus Anfrage, with the call slot beside it and quieter. An action, never navigation. THE SPLIT, and it is the whole point of this file. The tour page already carries a sticky bar at the TOP (`#tour-sticky-header`, `.tsh-*`, declared in tours/tour/book_form.blade.php). On a desktop that is the right place; on a phone the action belongs under the thumb. So: below 900 the bottom bar is on duty, the .tsh- top bar never appears 900 and up nothing changes: the .tsh- top bar behaves as it always has and this bar is not displayed at all There is ONE signal for both, and the booking panel's existing observer in book_form.blade.php produces it: `oc-tour-past-panel` on once `.booking-panel` has scrolled past the top of the viewport. Which bar that means is decided here, by width, and nowhere else. No second observer, no matchMedia number mirroring a rung in JavaScript. Mobile first on 600 / 900 / 1200 and no other width - `php artisan css:ladder` is the gate. Loaded from Us_cluster::frontend.tours.detail only, which is why the page-level rules below (body padding) are safe to write here. ========================================================================= */ /* --- 1. The page has to end above the bar -------------------------------- "Never covering the last section." The shell renders the footer after the content, so the room has to be taken at the page level, not inside the content column. base.css's `* { padding: 0 }` is a lower specificity than this, and neither app_r.css nor app_r_min.css touches body padding. */ body { padding-bottom: calc(64px + env(safe-area-inset-bottom, 0px)); } /* --- 2. Which bar is on duty --------------------------------------------- These beat the `#tour-sticky-header { display: none }` in book_form's own