/* =====================================================================
   BVX ACCOUNT STYLING
   Visual-only override layer for WooCommerce My Account pages.
   Colors, type, and spacing pulled directly from the wearbvx.com
   frontend design system. Every selector below is a stable, documented
   WooCommerce class name (woocommerce-*) or a generic form element
   scoped inside the account content area - nothing here depends on
   Hostinger AI theme's internal markup, so this should survive theme
   updates.
   ===================================================================== */

:root {
  --bvx-obsidian: #0A0A0A;
  --bvx-bone: #FAF7F2;
  --bvx-sulphur: #BCFF00;
  --bvx-border: rgba(0, 0, 0, 0.1);
  --bvx-bg-secondary: #F7F7F7;
  --bvx-text-muted: #888888;
}

/* ---------------------------------------------------------------------
   Page background + base type
   --------------------------------------------------------------------- */
/* v1.0.12 - padding-left/padding-right removed from this base rule.
   Confirmed via Web Inspector: .woocommerce-account is WooCommerce's own
   <body> class, so this horizontal padding was insetting the entire page
   (cream header, dark footer, everything) at desktop widths, not just
   the My Account content - the same authoring mistake already fixed for
   mobile in v1.0.11, just not previously caught at desktop. Confirmed the
   actual content wrapper (.entry-content.has-global-padding, the
   theme's own wrapper around .woocommerce-MyAccount-navigation and
   .woocommerce-MyAccount-content) already provides ~24px of its own
   horizontal gutter at desktop, independent of this plugin - so removing
   this rule's padding entirely (not replacing it elsewhere) is the
   complete fix: header/footer become full-width at every breakpoint, and
   My Account content keeps its intended spacing from the theme's own
   wrapper. The mobile override below (max-width: 768px, values already
   zeroed since v1.0.11) is left in place as a harmless no-op rather than
   removed, since the base value it overrides is now already 0. */
.woocommerce-account {
  background: var(--bvx-bone);
}

/* Heading clipping fix - v1.0.3
   Confirmed via Web Inspector: the page heading is NOT inside the
   WooCommerce content area padded above - it's a separate theme-generated
   title block (h1.hostinger-ai-page-title) that sits before
   .entry-content, with effectively zero margin of its own. The theme's
   fixed header (.hostinger-ai-menu, position:fixed, ~96px tall, plus an
   extra 32px when the WP admin bar is present) has no space reserved for
   it in normal flow, so it overlapped the title directly. v1.0.2's
   padding-top on .woocommerce-account never had a chance to fix this -
   it was padding a different, later element.
   Scoped to body.woocommerce-account so no page title outside My Account
   is touched, and scoped to the theme's own specific title class so no
   other wp-block-group on the page is affected. */
body.woocommerce-account h1.hostinger-ai-page-title {
  margin-top: 150px;
}

.woocommerce-account .woocommerce,
.woocommerce-account .woocommerce-MyAccount-content,
.woocommerce-account p,
.woocommerce-account li,
.woocommerce-account label {
  font-family: 'Inter', sans-serif;
  font-weight: 300;
  color: var(--bvx-obsidian);
  line-height: 1.6;
}

.woocommerce-account a {
  color: var(--bvx-obsidian);
  text-decoration: underline;
  text-underline-offset: 3px;
}

.woocommerce-account a:hover {
  opacity: 0.6;
}

/* ---------------------------------------------------------------------
   Headings - override the theme's default serif with Inter Tight
   --------------------------------------------------------------------- */
.woocommerce-account h1,
.woocommerce-account h2,
.woocommerce-account h3,
.woocommerce-account .entry-title,
.woocommerce-account .page-title {
  font-family: 'Inter Tight', sans-serif;
  font-weight: 900;
  letter-spacing: -0.02em;
  color: var(--bvx-obsidian);
  line-height: 1.05;
}

.woocommerce-account h1,
.woocommerce-account .entry-title,
.woocommerce-account .page-title {
  font-size: clamp(2rem, 4vw, 3rem);
  margin-bottom: 40px;
}

.woocommerce-account h2 {
  font-size: 1.3rem;
  margin-bottom: 16px;
}

/* ---------------------------------------------------------------------
   Account navigation (Dashboard / Orders / Addresses / etc.)
   --------------------------------------------------------------------- */
.woocommerce-MyAccount-navigation {
  border-right: none;
}

.woocommerce-MyAccount-navigation ul {
  list-style: none;
  margin: 0;
  padding: 0;
  display: flex;
  flex-direction: column;
  gap: 4px;
}

.woocommerce-MyAccount-navigation-link {
  border: none;
}

.woocommerce-MyAccount-navigation-link a {
  display: block;
  font-family: 'JetBrains Mono', monospace;
  font-size: 0.68rem;
  letter-spacing: 0.15em;
  text-transform: uppercase;
  color: var(--bvx-obsidian);
  text-decoration: none;
  opacity: 0.55;
  padding: 10px 0;
  border-bottom: 1px solid var(--bvx-border);
  transition: opacity 0.2s;
}

.woocommerce-MyAccount-navigation-link a:hover {
  opacity: 1;
}

.woocommerce-MyAccount-navigation-link.is-active a {
  opacity: 1;
  text-decoration: underline;
  text-underline-offset: 4px;
}

/* ---------------------------------------------------------------------
   Notices - v1.0.3: raised specificity with body.woocommerce-account,
   same proven approach already used for Addresses in v1.0.2. Also adding
   !important on the color/border properties specifically here (not used
   elsewhere in this file) - justified by direct evidence from Web
   Inspector that this theme's own CSS uses !important extensively (the
   confirmed .hostinger-ai-menu header rule does), so plain specificity
   may not be enough to win against it.
   --------------------------------------------------------------------- */
body.woocommerce-account .woocommerce-message,
body.woocommerce-account .woocommerce-info,
body.woocommerce-account .woocommerce-error,
body.woocommerce-account .woocommerce-noreviews {
  background: var(--bvx-bone) !important;
  border: 1px solid var(--bvx-border) !important;
  border-radius: 0 !important;
  color: var(--bvx-obsidian) !important;
  font-family: 'Inter', sans-serif;
  font-weight: 300;
  padding: 18px 20px;
  box-shadow: none !important;
  list-style: none;
}

/* Remove WooCommerce's default colored info icon - covers both a
   CSS-generated pseudo-element and a real inline icon element (svg/img),
   since the exact markup can vary. */
body.woocommerce-account .woocommerce-message::before,
body.woocommerce-account .woocommerce-info::before,
body.woocommerce-account .woocommerce-error::before {
  content: none !important;
  display: none !important;
}

body.woocommerce-account .woocommerce-message svg,
body.woocommerce-account .woocommerce-info svg,
body.woocommerce-account .woocommerce-error svg,
body.woocommerce-account .woocommerce-message img,
body.woocommerce-account .woocommerce-info img,
body.woocommerce-account .woocommerce-error img {
  display: none !important;
}

body.woocommerce-account .woocommerce-message a,
body.woocommerce-account .woocommerce-info a,
body.woocommerce-account .woocommerce-error a {
  font-family: 'JetBrains Mono', monospace;
  font-size: 0.65rem;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  color: var(--bvx-obsidian) !important;
}

/* v1.0.6 - WooCommerce Blocks notice (confirmed via Web Inspector on the
   Payment Methods "no saved methods" notice). This is a separate
   component from the classic .woocommerce-message/-info/-error markup
   above - it ships its own CSS (wc-blocks.css / packages-style.css),
   which is why the v1.0.3 classic-notice rules never matched it despite
   raised specificity and !important. Scoped strictly to the confirmed
   .is-info variant for now, not the base .wc-block-components-notice-
   banner class, since only .is-info has been confirmed in Safari. */
body.woocommerce-account .wc-block-components-notice-banner.is-info {
  background: var(--bvx-bone) !important;
  border: 1px solid var(--bvx-border) !important;
  border-radius: 0 !important;
  color: var(--bvx-obsidian) !important;
  font-family: 'Inter', sans-serif;
  font-weight: 300;
  box-shadow: none !important;
}

/* Confirmed via Web Inspector: the icon is a direct <svg> child of the
   banner (not a pseudo-element, not wrapped in an intermediate icon
   element), so it's targeted with a direct-child combinator rather than
   a descendant selector. */
body.woocommerce-account .wc-block-components-notice-banner.is-info > svg {
  display: none !important;
}

/* ---------------------------------------------------------------------
   Buttons - strip the theme's rounded pill styling
   --------------------------------------------------------------------- */
.woocommerce-account .button,
.woocommerce-account button,
.woocommerce-account input[type="submit"] {
  font-family: 'JetBrains Mono', monospace;
  font-size: 0.68rem;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  background: var(--bvx-sulphur);
  color: var(--bvx-obsidian);
  border: none;
  border-radius: 0;
  padding: 16px 32px;
  cursor: pointer;
  box-shadow: none;
  transition: opacity 0.2s;
}

.woocommerce-account .button:hover,
.woocommerce-account button:hover,
.woocommerce-account input[type="submit"]:hover {
  opacity: 0.85;
  background: var(--bvx-sulphur);
  color: var(--bvx-obsidian);
}

/* Secondary-style links that render as buttons in some templates */
.woocommerce-account .woocommerce-Button--secondary,
.woocommerce-account a.button.wp-element-button.woocommerce-button--secondary {
  background: transparent;
  border: 1px solid rgba(0, 0, 0, 0.25);
  color: var(--bvx-obsidian);
}

/* ---------------------------------------------------------------------
   Form inputs - clean rectangular fields, no rounded corners
   --------------------------------------------------------------------- */
.woocommerce-account input[type="text"],
.woocommerce-account input[type="email"],
.woocommerce-account input[type="password"],
.woocommerce-account input[type="tel"],
.woocommerce-account select,
.woocommerce-account textarea {
  font-family: 'JetBrains Mono', monospace;
  font-size: 0.85rem;
  color: var(--bvx-obsidian);
  background: transparent;
  border: 1px solid var(--bvx-border);
  border-radius: 0;
  padding: 14px 16px;
  width: 100%;
  box-shadow: none;
  transition: border-color 0.2s;
}

.woocommerce-account input[type="text"]:focus,
.woocommerce-account input[type="email"]:focus,
.woocommerce-account input[type="password"]:focus,
.woocommerce-account input[type="tel"]:focus,
.woocommerce-account select:focus,
.woocommerce-account textarea:focus {
  outline: none;
  border-color: var(--bvx-obsidian);
}

.woocommerce-account .form-row label {
  font-family: 'JetBrains Mono', monospace;
  font-size: 0.62rem;
  letter-spacing: 0.15em;
  text-transform: uppercase;
  opacity: 0.6;
  margin-bottom: 8px;
  display: block;
}

/* ---------------------------------------------------------------------
   Login / Register - two-column layout (WooCommerce's own u-column
   classes), stripped of the theme's boxed/shadowed card look
   --------------------------------------------------------------------- */
.woocommerce-account .u-columns.col2-set {
  display: flex;
  flex-wrap: wrap;
  align-items: flex-start;
  gap: 40px;
}

.woocommerce-account .u-column1.col-1,
.woocommerce-account .u-column2.col-2 {
  box-sizing: border-box;
  float: none;
  width: auto;
  flex: 1 1 320px;
  margin: 0;
  padding: 32px;
  border: 1px solid var(--bvx-border);
  background: transparent;
}

.woocommerce-form-login,
.woocommerce-form-register {
  border: none;
}

.woocommerce-account .woocommerce-form-login__rememberme {
  font-family: 'Inter', sans-serif;
  font-size: 0.85rem;
}

/* ---------------------------------------------------------------------
   Addresses - v1.0.4
   Confirmed via Web Inspector: the Addresses wrapper carries
   .u-columns.woocommerce-Addresses.col2-set.addresses together - the
   same .u-columns.col2-set classes the Login/Register wrapper above
   uses. The old ".woocommerce-Addresses" selector (2 classes + element)
   was losing the cascade to the Login/Register rule's
   ".woocommerce-account .u-columns.col2-set" (3 classes) purely on
   class-count, so this stayed flex instead of grid. Same conflict
   existed one level down: the Login/Register column rule below also
   matches these boxes (.u-column1.col-1 / .u-column2.col-2), so the
   child selector is raised to match too. Both now target the confirmed
   real classes unique to this wrapper so they outrank the Login/Register
   rules without touching them. Desktop-only; mobile override below is
   unchanged.
   --------------------------------------------------------------------- */
body.woocommerce-account .u-columns.col2-set.addresses {
  display: grid;
  grid-template-columns: 1fr 1fr;
  gap: 40px;
  box-sizing: border-box;
  width: 100%;
}

/* v1.0.5 - WooCommerce's own clearfix on this wrapper generates ::before/
   ::after content. Once the wrapper became display:grid, those generated
   nodes became grid items too (auto-placed in source order alongside the
   two real .woocommerce-Address children), which is what pushed Billing
   into cell 2 (upper-right) and wrapped Shipping to cell 3 (lower-left).
   Removed from layout here only - the Login/Register wrapper still relies
   on this same clearfix via .col2-set::before/::after and is untouched. */
body.woocommerce-account .u-columns.col2-set.addresses::before,
body.woocommerce-account .u-columns.col2-set.addresses::after {
  display: none;
}

body.woocommerce-account .u-columns.col2-set.addresses .woocommerce-Address {
  box-sizing: border-box;
  float: none;
  width: auto;
  margin: 0;
  padding: 0;
  /* v1.0.5 - neutralizes the flex:1 1 320px inherited from the generic
     Login/Register column rule above. Inert under display:grid (flex-*
     properties have no effect on a grid item), kept for isolation only
     in case the parent's display value ever changes. */
  flex: none;
}

.woocommerce-Address-title h2 {
  display: inline;
  font-size: 1.1rem;
}

.woocommerce-Address-title .edit,
.woocommerce-Address-title a {
  font-family: 'JetBrains Mono', monospace;
  font-size: 0.62rem;
  letter-spacing: 0.1em;
  text-transform: uppercase;
}

.woocommerce-Address address {
  font-style: normal;
  border-top: 1px solid var(--bvx-border);
  padding-top: 16px;
  margin-top: 16px;
  line-height: 1.8;
}

/* ---------------------------------------------------------------------
   Orders table (list) + single order detail
   --------------------------------------------------------------------- */
.woocommerce-orders-table {
  border-collapse: collapse;
  width: 100%;
}

.woocommerce-orders-table thead th {
  font-family: 'JetBrains Mono', monospace;
  font-size: 0.6rem;
  letter-spacing: 0.15em;
  text-transform: uppercase;
  opacity: 0.5;
  text-align: left;
  padding: 12px 8px;
  border-bottom: 1px solid var(--bvx-border);
  font-weight: 400;
}

.woocommerce-orders-table__row td {
  padding: 16px 8px;
  border-bottom: 1px solid var(--bvx-border);
  font-family: 'Inter', sans-serif;
  font-size: 0.9rem;
}

.woocommerce-orders-table__cell-order-status {
  font-family: 'JetBrains Mono', monospace;
  font-size: 0.65rem;
  letter-spacing: 0.1em;
  text-transform: uppercase;
}

.woocommerce-order-details,
.woocommerce-customer-details {
  margin-top: 32px;
}

.woocommerce-table--order-details {
  border-collapse: collapse;
  width: 100%;
}

.woocommerce-table--order-details th,
.woocommerce-table--order-details td {
  border-bottom: 1px solid var(--bvx-border);
  padding: 14px 8px;
  font-family: 'Inter', sans-serif;
}

.woocommerce-table--order-details tfoot th,
.woocommerce-table--order-details tfoot td {
  font-family: 'Inter Tight', sans-serif;
  font-weight: 700;
}

/* ---------------------------------------------------------------------
   Account details - password change fieldset
   --------------------------------------------------------------------- */
.woocommerce-EditAccountForm fieldset {
  border: 1px solid var(--bvx-border);
  padding: 24px;
  margin: 24px 0;
}

.woocommerce-EditAccountForm fieldset legend {
  font-family: 'JetBrains Mono', monospace;
  font-size: 0.62rem;
  letter-spacing: 0.15em;
  text-transform: uppercase;
  opacity: 0.6;
  padding: 0 8px;
}

/* v1.0.13 - Desktop-only: removes the original vertical sidebar nav from
   layout entirely, now that Shop Chrome v1.0.10 renders the same
   WooCommerce account navigation as a header nav instead. display:none
   (not the visually-hidden pattern used for the v1.0.11 mobile title
   hide) is deliberate here - the header nav is a complete, semantic
   <nav> exposing the identical set of links, so leaving this sidebar
   merely visually hidden would leave keyboard/screen-reader users
   tabbing through the same six links twice with no visible copy.
   Scoped to min-width:769px only - mobile, where this sidebar remains
   the only account navigation, is completely unchanged. */
@media (min-width: 769px) {
	body.woocommerce-account .woocommerce-MyAccount-navigation {
		display: none !important;
	}
}

/* v1.0.14 - Desktop-only. .woocommerce-MyAccount-content was still
   floated at its old fraction of the row (a WooCommerce core default,
   never set by this plugin) after the sidebar above was removed from
   flow, leaving the freed-up space as blank margin instead of being used
   by the content. This is the smallest override that fixes it - only
   this element's float/width, nothing else. */
@media (min-width: 769px) {
	body.woocommerce-account .woocommerce-MyAccount-content {
		float: none;
		width: 100%;
	}
}

/* ---------------------------------------------------------------------
   Mobile refinement pass - v1.0.7
   Single breakpoint (max-width: 768px), same as the v1.0.2-v1.0.6
   "conservative" block this replaces. Desktop styling above is entirely
   unchanged - every rule in this block is additive or overrides a value
   only within this media query. Header/footer (global Hostinger chrome)
   is intentionally NOT touched here - tracked as a separate sitewide
   task. Covers: tighter page-title sizing, evidence-based header
   clearance, denser navigation, smaller body text, tighter Login/
   Register and Addresses cards, more compact form fields/buttons/
   notices/password fieldset, stacked First/Last Name, and reduced page
   gutters.
   --------------------------------------------------------------------- */
@media (max-width: 768px) {

  /* Page gutters - v1.0.11. Confirmed via Web Inspector: this rule was
     padding the <body> element itself (.woocommerce-account is
     WooCommerce's own body class), which meant it was insetting the
     cream header and dark footer along with the account content - not
     just the content, as originally intended. The header/footer inset
     traced directly back to this rule, not to any header/footer
     selector. Confirmed via Web Inspector that the account content
     already has its own ~24px horizontal gutter from the theme's own
     .entry-content.has-global-padding wrapper around .woocommerce, so
     zeroing this out here does not remove all mobile gutter from the
     content - it removes the double-padding this rule was adding on
     top of what the theme already provides, while letting header and
     footer become full-width. */
  .woocommerce-account {
    padding-left: 0;
    padding-right: 0;
  }

  /* Page title - confirmed via Web Inspector at 393px width: the fixed
     .hostinger-ai-menu header is 104px tall (position:fixed, top:0) on
     mobile - no WP admin-bar allowance needed here, since WP core hides
     the admin bar below 782px. Same method as the confirmed desktop
     value (96px header + 32px admin-bar + 22px breathing room = 150px):
     104px header + 22px breathing room = 126px. */
  body.woocommerce-account h1.hostinger-ai-page-title {
    margin-top: 126px;
  }

  /* Title sizing tightened further per review - target ~1.6rem max
     rather than the previous 2.2rem ceiling. */
  .woocommerce-account h1,
  .woocommerce-account .entry-title,
  .woocommerce-account .page-title {
    font-size: clamp(1.35rem, 5.5vw, 1.6rem);
    margin-bottom: 20px;
  }

  .woocommerce-account h2 {
    font-size: 1.1rem;
    margin-bottom: 12px;
  }

  /* Body text - Dashboard intro, Addresses intro/address text, Account
     Details helper text. No explicit font-size existed before this
     (desktop rule leaves it at the theme default), so this is a new
     mobile-only addition rather than an override of an existing value. */
  .woocommerce-account p,
  .woocommerce-account li,
  .woocommerce-account .woocommerce-MyAccount-content {
    font-size: 0.85rem;
    line-height: 1.5;
  }

  /* Navigation - denser rows. */
  .woocommerce-MyAccount-navigation-link a {
    font-size: 0.62rem;
    letter-spacing: 0.1em;
    padding: 8px 0;
    line-height: 1.2;
  }

  /* Login/Register cards - was padding:24px, margin-bottom:24px. */
  .woocommerce-account .u-column1.col-1,
  .woocommerce-account .u-column2.col-2 {
    width: 100%;
    float: none;
    margin-bottom: 20px;
    padding: 20px;
  }

  /* Addresses grid - stacked single column unchanged; gap tightened. */
  body.woocommerce-account .woocommerce-Addresses,
  body.woocommerce-account .u-columns.col2-set.addresses {
    grid-template-columns: 1fr;
    gap: 24px;
  }

  .woocommerce-Address address {
    line-height: 1.5;
    padding-top: 12px;
    margin-top: 12px;
  }

  /* Form fields - was padding:14px 16px, font-size:0.85rem. */
  .woocommerce-account input[type="text"],
  .woocommerce-account input[type="email"],
  .woocommerce-account input[type="password"],
  .woocommerce-account input[type="tel"],
  .woocommerce-account select,
  .woocommerce-account textarea {
    padding: 11px 14px;
    font-size: 0.8rem;
  }

  .woocommerce-account .form-row label {
    font-size: 0.58rem;
    letter-spacing: 0.12em;
    margin-bottom: 6px;
  }

  /* Account Details - First Name / Last Name stacked full-width instead
     of side-by-side, per review. */
  .woocommerce-account .form-row-first,
  .woocommerce-account .form-row-last {
    float: none;
    width: 100%;
  }

  /* Notices - classic (.woocommerce-message/-info/-error) and the
     confirmed WooCommerce Blocks notice banner. Styling the banner
     itself only - confirmed via Web Inspector that "Add payment method"
     is a separate <a class="button"> after the notice, not inside it,
     so it's already covered by the general button rule below and needs
     no notice-specific CTA selector. */
  body.woocommerce-account .woocommerce-message,
  body.woocommerce-account .woocommerce-info,
  body.woocommerce-account .woocommerce-error,
  body.woocommerce-account .woocommerce-noreviews,
  body.woocommerce-account .wc-block-components-notice-banner.is-info {
    padding: 14px 16px;
  }

  /* Buttons - was padding:16px 32px, font-size:0.68rem. */
  .woocommerce-account .button,
  .woocommerce-account button,
  .woocommerce-account input[type="submit"] {
    padding: 12px 24px;
    font-size: 0.62rem;
  }

  /* Password fieldset - was padding:24px, margin:24px 0. */
  .woocommerce-EditAccountForm fieldset {
    padding: 16px;
    margin: 16px 0;
  }

  .woocommerce-EditAccountForm fieldset legend {
    font-size: 0.58rem;
  }

  /* Orders table - unchanged from v1.0.2, stacked card layout. */
  .woocommerce-orders-table thead {
    display: none;
  }

  .woocommerce-orders-table__row {
    display: block;
    border-bottom: 1px solid var(--bvx-border);
    padding: 12px 0;
  }

  .woocommerce-orders-table__row td {
    display: block;
    border-bottom: none;
    padding: 4px 0;
  }

  /* v1.0.8 - Mobile My Account header fix.
     Confirmed via Web Inspector: .hostinger-ai-menu-wrapper appears
     TWICE in the DOM - an outer instance that is a direct child of
     .wp-site-blocks (a 96px-tall grid spacer reserving space for the
     fixed header: padding-top:24px, padding-bottom:24px), and a second,
     nested instance inside .hostinger-ai-menu that holds the real,
     visible header content. The child-combinator selector below was
     verified in Safari's Elements-panel selector search to return
     exactly one match - the outer spacer - confirming it cannot also
     hide the real header content.
     Hiding only that outer spacer, then setting the header itself to
     position:relative (kept as a positioning context for any of its
     own absolutely-positioned children, rather than position:static,
     which would remove that), returns .hostinger-ai-menu to normal
     document flow on mobile My Account pages only: it now pushes
     content down by its own real height and scrolls away with the
     page, instead of staying pinned over it.
     With the header back in normal flow, the v1.0.7 h1.hostinger-ai-
     page-title margin-top:126px value (a manual compensation for a
     fixed header that occupied no flow space) is no longer the correct
     model - that rule above is left in place unmodified per this
     revision's scope, but is superseded here by margin-top:0 !important
     on the same selector, exactly matching what was live-tested in
     Safari. This is a diagnostic zero value, not a final one - a small
     deliberate breathing-room gap will be reassessed in v1.0.9 once the
     natural-flow result has been confirmed on device.
     Scoped strictly to body.woocommerce-account at max-width:768px -
     desktop and the rest of the site are completely unaffected. */
  body.woocommerce-account .wp-site-blocks > .hostinger-ai-menu-wrapper {
    display: none !important;
  }

  body.woocommerce-account .hostinger-ai-menu {
    position: relative !important;
    top: 0 !important;
  }

  body.woocommerce-account h1.hostinger-ai-page-title {
    margin-top: 0 !important;
  }

  /* v1.0.9 - Mobile My Account: removes the theme's fixed-header
     compensation padding, now unnecessary since v1.0.8 returned
     .hostinger-ai-menu to normal flow on these pages. Confirmed via
     Web Inspector: the winning rule was
     body.hostinger-ai-builder-elementor / -gutenberg { padding-top: 75px; },
     a sitewide theme rule keyed off the builder body-class, not scoped
     to My Account. Overriding only padding-top (not the padding
     shorthand) here has no effect on the existing padding-left/
     padding-right gutters, which are separate longhand properties set
     elsewhere in this file. */
  body.woocommerce-account {
    padding-top: 0 !important;
  }

  /* v1.0.9 - Mobile My Account title size. Confirmed via Web Inspector:
     the theme's .has-x-large-font-size { font-size: var(...) !important; }
     (part of WordPress block-editor's font-size preset classes) was
     winning over the v1.0.7 mobile title rule despite that rule's lower
     specificity - this theme class also carries !important, so a plain
     specificity increase wasn't enough on its own. This rule matches it
     with !important plus higher specificity (element+class+element+
     class vs. the theme's single class) so it wins reliably. The v1.0.7
     rule targeting .woocommerce-account h1/.entry-title/.page-title
     generally is left unchanged and still applies as the baseline for
     any title element that isn't specifically h1.hostinger-ai-page-title. */
  body.woocommerce-account h1.hostinger-ai-page-title {
    font-size: clamp(1.35rem, 5.5vw, 1.6rem) !important;
  }

  /* v1.0.10 - Mobile My Account: removes the header's hamburger/
     responsive-navigation trigger and the blank drawer it opens.
     shop.wearbvx.com doesn't need its own mobile nav menu - the main
     BVX storefront navigation lives on wearbvx.com - and the opened
     drawer was confirmed empty/non-functional.
     Confirmed via Web Inspector: the toggle
     (button.wp-block-navigation__responsive-container-open, aria-
     label="Open menu") and the drawer it opens
     (div#modal-1.wp-block-navigation__responsive-container) are both
     children of one outer nav.wp-block-navigation element, which sits
     inside .hostinger-ai-site-navigation-wrapper. The WooCommerce
     customer-account block and mini-cart block are confirmed separate
     sibling elements after this <nav>, not nested inside it or its
     drawer, so hiding the <nav> cannot affect them. That wrapper's
     computed layout is confirmed is-layout-flex (not an explicit fixed-
     column grid), so removing the <nav> lets the remaining flex items
     (logo, account, cart) close the space naturally - no leftover
     blank track, no second selector needed. Scoped to the <nav> inside
     .hostinger-ai-menu specifically (not the whole
     .hostinger-ai-site-navigation-wrapper, which also contains the
     account/cart siblings) so only the nav block and its own drawer are
     removed. */
  body.woocommerce-account .hostinger-ai-menu nav.wp-block-navigation {
    display: none !important;
  }

  /* v1.0.11 - Mobile My Account: visually hides the page title
     (h1.hostinger-ai-page-title) while keeping it in the DOM and
     available to assistive technology, per design preference - the
     active nav item already communicates which page the customer is
     on, and repeating it as a large heading was judged unnecessary on
     mobile. Confirmed via device testing that the title itself renders
     correctly (this is a deliberate style choice, not a bug fix). Uses
     the standard visually-hidden/screen-reader-only pattern (the same
     technique WordPress core uses for .screen-reader-text) rather than
     display:none or visibility:hidden, both of which would also remove
     the heading from the accessibility tree. */
  body.woocommerce-account h1.hostinger-ai-page-title {
    position: absolute !important;
    width: 1px !important;
    height: 1px !important;
    padding: 0 !important;
    margin: -1px !important;
    overflow: hidden !important;
    clip: rect(0, 0, 0, 0) !important;
    white-space: nowrap !important;
    border: 0 !important;
  }
}