From d83c89f28735a1a8402e2b80dec079b40fc9f7de Mon Sep 17 00:00:00 2001 From: Doxa Maps Date: Wed, 30 Sep 2026 03:07:19 +0000 Subject: [PATCH] =?UTF-8?q?Phones:=20the=20gallery's=20=E2=98=B0=20moves?= =?UTF-8?q?=20into=20a=20bar=20above=20the=20pane,=20off=20every=20map?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The floating ☰ circle sat in the bottom-left corner of whatever map was open. It covered Simple Research's search box and the licence credit on Cities and Gospel Resources (in Arabic, mirrored, the credit's other end). On a phone (narrow and headerless, the circle's own condition) the ☰ now sits in a 44px bar above the pane, beside the open view's name. The layout no longer publishes a fab clearance, so the maps' bottom corners return to their plain insets. Desktop and header-on layouts are unchanged. --- library/layouts/VerticalTabsLayout.vue | 41 +++++++++++++++++++++----- 1 file changed, 34 insertions(+), 7 deletions(-) diff --git a/library/layouts/VerticalTabsLayout.vue b/library/layouts/VerticalTabsLayout.vue index d6fbc02db..1989dc3e4 100644 --- a/library/layouts/VerticalTabsLayout.vue +++ b/library/layouts/VerticalTabsLayout.vue @@ -103,7 +103,7 @@ sit NEXT TO the circle rather than on top of it (12px inset + 44px button + 8px gap). A consumer that hardcoded 64px would silently overlap the day the circle resizes; reading it means the circle's geometry is stated once, here, by the component that owns it. --> -
+ ★ THE PHONE BAR REPLACED THE FLOATING CIRCLE (mobile pass, 2026-09-30). The circle floated over + whatever each map put in its bottom-left corner: Simple Research's search box, and the licence + credit on Cities and Gospel Resources (measured at 390, en and ar). No placement of a floating + button is free on every map, so on a phone the ☰ lives in a 44px bar ABOVE the pane, with the + open view's name beside it, and covers nothing. It stays while the drawer is open: its ☰ + closes the drawer again. The button keeps the vtl-menu class, which is how + check:nav-reachable-mobile finds the rail's opener. --> +
+ + {{ activeLabel }} +