From cb677b35453b81105f7cb1f3fe1230db4d004e4b Mon Sep 17 00:00:00 2001 From: Louis King Date: Fri, 3 Jul 2026 00:14:28 +0100 Subject: [PATCH] fix(web): stop closed mobile nav from intercepting page clicks The two-column mobile nav set display:block on #mobile-nav (an ID selector) to override .menu's display:flex so column-count worked. That ID specificity also beat DaisyUI's closed-state display:none rule, so the menu stayed display:block while 'closed' (only opacity dropped to 0). The invisible, two-column-wide overlay captured clicks over underlying page content and fired SPA navigation. Scope display:block (and the column layout) to the dropdown's open state (.dropdown-open / :focus-within) so DaisyUI's display:none can hide the menu and its links when closed. --- src/meshcore_hub/web/static/css/app.css | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/meshcore_hub/web/static/css/app.css b/src/meshcore_hub/web/static/css/app.css index 4bab672..0ab0c51 100644 --- a/src/meshcore_hub/web/static/css/app.css +++ b/src/meshcore_hub/web/static/css/app.css @@ -424,7 +424,8 @@ font-size: 0.9375rem; } - #mobile-nav { + .dropdown.dropdown-open #mobile-nav, + .dropdown:focus-within #mobile-nav { display: block; column-count: 2; column-gap: 0.25rem;