From 1908d6f5f9d63da5e53bdf92f4cbefddfb1b7a91 Mon Sep 17 00:00:00 2001 From: Maurice Date: Thu, 17 Sep 2026 15:02:58 +0200 Subject: [PATCH] fix(dawarich): the places rail scrolls again with the panel open MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The panel sat in a wrapper that could not shrink and did not scroll, so opening it took whatever height the day's stays needed — forty of them is over 3000px — and squeezed the places list, which is the flex child that scrolls, down to nothing. The rail stopped scrolling and most of the stays sat below the bottom edge with no way to reach them. The wrapper is capped at half the rail and scrolls on its own. Open, the stays are all reachable and the list underneath is still a list; shut, nothing changes, because the cap only bites once the content passes it. --- client/src/components/Planner/PlacesSidebar.tsx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/client/src/components/Planner/PlacesSidebar.tsx b/client/src/components/Planner/PlacesSidebar.tsx index fcd40f0cf..a9d5f6f9b 100644 --- a/client/src/components/Planner/PlacesSidebar.tsx +++ b/client/src/components/Planner/PlacesSidebar.tsx @@ -70,7 +70,13 @@ const PlacesSidebar = React.memo(function PlacesSidebar(props: PlacesSidebarProp nothing at all when there is nothing pending — an integration that is connected and quiet should be invisible rather than a permanent empty card. */} -
+ {/* Capped and scrolling on its own. Open, the panel is as tall as the day has stays — + ten of them on a day of driving — and with nothing holding it back it pushed the + places list, which is the flex child that scrolls, down to nothing: the rail + stopped scrolling and half the stays sat below the bottom edge with no way to + reach them. Half the rail at most, so the list it sits above is always still a + list. */} +