/* ==========================================================
   Aplify – Responsive Token Overrides
   --------------------------------------------------------------
   Base :root token values are emitted by PHP from the plugin's
   settings page (see settings/tokens-output.php). This file holds
   ONLY the breakpoint-specific overrides, which are not user-
   editable from the admin UI but can be tweaked here per-client
   if needed.
   ========================================================== */

@media (min-width: 1400px) {
  :root {
    --gap-max: 36px;
    --field-h: 60px;
    --label-size: 1rem;
    /* Nudged, not doubled: these do something now, and an 18px chevron reads
       as an icon rather than an affordance. Tracks the larger --field-h at
       this breakpoint without becoming the loudest thing in the field. */
    --chevron-size: 14px;
    --chevron-offset: 18px;
  }
}

@media (max-width: 480px) {
  :root {
    --field-h: 48px;
    --radius: 14px;
    --btn-radius: 999px;
    --menu-extra: 80px;
    --menu-w-max: 92vw;
    --button-shadow: none;
    --button-shadow-hover: none;
  }
}

/* ----------------------------------------------------------
   Pagination scroll target offset.
   Lets site owners control how much breathing room is left
   above the results section when paginating. Configurable
   from Settings → Aplify Integration → Design Tokens → Misc.
---------------------------------------------------------- */
[x-data="aplifySearchResults"] {
    scroll-margin-top: var(--scroll-margin);
}

/* ==========================================================
   BASELINE WEIGHT — the plugin's roots stop inheriting the theme's

   Found out of the box on Twenty Twenty-Five: body is font-weight 300, so
   every element in the plugin without its own weight rendered at 300 —
   closing dates, card footers, anything relying on inheritance. On a theme
   with a 600 body it would have gone the other way. The plugin's type
   hierarchy cannot be "considered" while its baseline is whatever the host
   theme happens to set.

   These are the shortcode roots and the apply-flow body. Declaring the
   baseline HERE rather than on each element keeps it a single statement, and
   every rule inside still overrides it normally — this only catches what
   would otherwise fall through to the theme.

   Deliberately not `!important` and deliberately low specificity: a client
   who genuinely wants their theme's weight can still override it.
   ========================================================== */
.aplify-search-form-container,
.aplify-search-results,
.aplify-apply-form,
.aplify-events,
.aplify-job-description,
.aplify-recently-viewed,
.aplify-map-view,
.aplify-thanks,
body.aplify-flow {
  font-weight: var(--weight-body, 400);
}