/* ========================================================================== MaoriMe standard mobile layout (Layer 1 - responsive CSS safety net) -------------------------------------------------------------------------- One shared, client-agnostic mobile presentation for the v3 login / registration / password-recovery / logged-in shell pages: LogonWeb2.aspx, Default_Login.aspx and the unbranded root Default.aspx. This is the SAFETY NET half of the "hybrid layered on CSS" approach. Layer 2 (a viewport cookie read in Page_PreInit) stops the client skin from being EMITTED on mobile, but this stylesheet guarantees the mobile layout is visually correct even when the skin IS present in the DOM - first visit before the cookie exists, cookies disabled, or the instant a viewport crosses the breakpoint before the one-time reload happens. Strategy (viewport-driven, NOT server-side device detection): loaded LAST in (after the client head-CSS literal), the resets use !important + high specificity so they beat the theme stylesheets AND the inline background written onto the tag by lit_BodyTag (inline styles otherwise win on source order alone). Only the VISUAL skin is standardised - client data/config (registration questions, hapu/iwi options, consent, routing) is untouched. Breakpoint: 767.98px. Bootstrap 3.4.1 xs/sm boundary is 768px; 767.98px cleanly claims the mobile side of the seam the client skins' own @media (max-width:768px) rules sit on. ========================================================================== */ /* Desktop / larger screens: the standard mobile chrome is hidden so the existing client skin shows exactly as before. These are the always-on defaults for the .mobile/.desktop convention (previously supplied by the client-gated st_Mobile