Area: Forums (audit p2) · Surface: GET /forums/{slug}/settings on mobile-v2 (templates/forums/settings.php .fs-savebar) · Dimension: Law 5 — mobile first-class · Severity: minor
On mobile, the forum settings 'unsaved changes' floating save bar is fixed at bottom:18px and overlaps the mobile-v2 bottom tab bar, covering the primary app navigation while editing settings. Law 5 (mobile first-class).
Evidence
settings.php has no mobile variant (comm of templates/forums vs templates/mobile/forums shows settings.php only in desktop set), so on phones it renders inside the mobile-v2 chrome (BaseController::render() falls back to the desktop template; mobile/base.php wraps it with .mobile-tabbar). The save bar is fixed at the very bottom: settings.php:442 .fs-savebar{position:fixed;bottom:18px;left:50%;...;z-index:30}. The mobile tab bar sits at bottom:0: mobile-v2.css:357-360 .mobile-tabbar{position:sticky;bottom:0;z-index:20;...}. The z-30 fixed save-bar floats over and covers the z-20 bottom navigation.
Suggested fix. Offset the save bar above the tab bar on mobile-v2 (e.g. body.mobile-v2 .fs-savebar{bottom:calc(var(--m-tabbar-height) + env(safe-area-inset-bottom) + 12px)}) or build a settings mobile variant.
Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.
Patrick Bass
@mobieus