/* * This is a manifest file that'll be compiled into application.css. * * With Propshaft, assets are served efficiently without preprocessing steps. You can still include * application-wide styles in this file, but keep in mind that CSS precedence will follow the standard * cascading order, meaning styles declared later in the document or manifest will override earlier ones, * depending on specificity. * * Consider organizing styles into separate files for maintainability. */ /* Installed-PWA app chrome. The inline script adds `pwa` to in standalone display mode; here we swap the web header/footer for the bottom tab bar (see shared/_mobile_tab_bar). Inert on the desktop web. */ #pwa-tab-bar { display: none; } .pwa #pwa-tab-bar { display: block; } .pwa body > header, .pwa body > footer, .pwa [data-donate-fab] { display: none; } /* With the web header hidden in the PWA, pad for the notch/status bar (top) and the tab bar + home indicator (bottom). Needs viewport-fit=cover (set in the layout) for the safe-area insets to be non-zero on iOS/Android. */ .pwa body { padding-top: env(safe-area-inset-top); padding-bottom: calc(3.75rem + env(safe-area-inset-bottom)); }