/*
 * WAYZAWAY NATIVE DOUBLE LOADER R1
 *
 * Android and iOS wrappers already provide their own native
 * navigation/loading indicator.
 *
 * Pricing and Favourites also activate web-side loading
 * visuals. In installed native apps that can result in two
 * simultaneous spinners.
 *
 * Keep every existing loading controller, backdrop, timing
 * and readiness gate. Suppress only the duplicate WEB visual
 * in native app mode.
 */


/* ==========================================================
   PRICING

   Keep ::before, which is the existing page-protection mask.
   Hide only ::after, which is the Pricing web spinner.
   ========================================================== */

html.wz-native-app.wz-r1i-pricing-loading::after {
  display: none !important;
  content: none !important;
  animation: none !important;
}


/* ==========================================================
   FAVOURITES

   The favourites flash guard is retained. R1MA normally
   displays the shared #wz-single-loading-visual-r1 spinner
   whenever that guard is active.

   In Android/iOS the native wrapper already supplies the
   visible loading indicator, so suppress only that shared
   web spinner while the favourites guard exists.

   :has() is supported by the current Android System WebView
   and WKWebView generations used by WayzAway.
   ========================================================== */

html.wz-native-app:
has(#wz-favourites-flash-guard-r1-mask)
#wz-single-loading-visual-r1 {
  display: none !important;
}


/*
 * Defensive variant for the period where the favourites
 * guard is explicitly active.
 */
html.wz-native-app:
has(#wz-favourites-flash-guard-r1-mask.wz-active)
#wz-single-loading-visual-r1 {
  display: none !important;
}


/*
 * Do not alter any mask/backdrop.
 * Do not hide the favourites guard itself.
 * Do not affect ordinary Chrome/Safari/web sessions.
 */