PR State:
merged
PR:
#674
Commit:
2b30b5aca16603d908bfbf806a005d8ac0d2775b
[FIX] web_responsive: restore mobile breadcrumb visibility
On a mobile-width screen the navbar breadcrumb could be squeezed to
zero width, so a user could not tell which record they were on, and
mobile tours hung at the first breadcrumb step until the watchdog
fired.
The apps-menu control was rendering twice on small screens: the
`t-else` branch was empty while the grid button sat outside it, so
mobile paid for two controls doing one job. Move the grid button
inside `t-else` so only the wide-screen layout renders it, matching
the template's own one-or-the-other intent and freeing width back to
the breadcrumb.
The breadcrumb itself had no minimum width and was the only
shrinkable element in the navbar, so every systray icon a module adds
is paid for out of the breadcrumb, down to zero. Give it a floor on
small viewports and let the systray shrink/scroll instead, so this
whole class of defect - not just this one instance - becomes
impossible.
TOGGLE_HOME_MENU_BUTTON in the navbar dereferenced a ref that no
longer renders on mobile; guard it so it is a no-op when the button
is absent, reproducing the previous mobile behaviour exactly.
Tests: assert the small-screen navbar exposes exactly one apps
control, plus the wide-screen counterpart.
Signed-off-by: David Tran <david.tran@tvtmarine.com>
Branch:
18.0