/* A CSS grid (not flex) so .plx-property-meta can sit between the header and
   the actions in source order — needed so .plx-property-actions can move to
   below .plx-property-meta on narrow screens via grid-template-areas — while
   still rendering in the exact same two-row arrangement as before on desktop
   (header+actions side by side, meta spanning beneath, zero gap between
   them, matching the original flex layout's measured positions exactly). */
.plx-property-header-row {
  align-items: center;
  column-gap: var(--space-3);
  display: grid;
  grid-template-areas:
    "header actions"
    "meta meta";
  grid-template-columns: 1fr auto;
  row-gap: 0;
}

.plx-property-header {
  align-items: center;
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-3);
  grid-area: header;
  margin-bottom: var(--space-1);
}
.plx-property-header .plx-section-title {
  font-size: var(--text-xl);
}

.plx-property-actions {
  align-items: center;
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-3);
  grid-area: actions;
  justify-self: end;
}

.plx-property-meta {
  align-items: center;
  color: var(--text-muted);
  display: flex;
  flex-wrap: wrap;
  font-size: var(--text-base);
  gap: var(--space-2);
  grid-area: meta;
}

@media (max-width: 767.98px) {
  .plx-property-header-row {
    grid-template-areas:
      "header"
      "meta"
      "actions";
    grid-template-columns: 1fr;
    row-gap: var(--space-3);
  }

  .plx-property-actions {
    justify-self: start;
  }
}

.plx-property-meta-sep {
  color: var(--text-subtle);
}

.plx-detail-grid {
  column-gap: 60px;
  display: grid;
  grid-template-columns: 1fr 1fr;
  row-gap: var(--space-4);
}

.plx-detail-row {
  display: flex;
  flex-direction: column;
  gap: var(--space-2);
}

.plx-detail-label {
  color: var(--text-muted);
  font-size: var(--text-sm);
  font-weight: var(--weight-medium);
  letter-spacing: 0.03em;
  /* text-transform: uppercase; */
}

.plx-detail-value {
  color: var(--text-primary);
  font-size: var(--text-base);
  font-weight: var(--weight-medium);
}

.plx-room-number-grid {
  display: grid;
  gap: 15px;
  grid-template-columns: repeat(auto-fill, minmax(87px, 1fr));
}

.plx-floor-card-header {
  align-items: center;
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-3);
  justify-content: space-between;
}

@media (max-width: 575.98px) {
  .plx-detail-grid {
    grid-template-columns: 1fr;
  }
}

.plx-info-banner {
  background: rgba(154, 162, 255, 0.12);
  border-left: 5px solid var(--pm-accent);
  border-radius: var(--radius-sm);
  color: var(--color-info);
  font-size: var(--text-base);
  font-weight: var(--weight-regular);
  padding: 15px;
}

/* ---- Create-property wizard chrome (header / body / footer) ---- */
.plx-wizard-card {
  padding: 0;
}

.plx-wizard-panel-header {
  align-items: center;
  border-bottom: 1px solid var(--border-default);
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-3);
  justify-content: space-between;
  padding: 15px 25px;
}

.plx-wizard-panel:not([data-plx-wizard-step="1"]):not([data-plx-wizard-step="2"]) .plx-wizard-panel-header {
  border-bottom: 0;
}

.plx-wizard-panel-title {
  color: var(--text-primary);
  font-size: 16px;
  font-weight: var(--weight-medium);
}

.plx-wizard-panel-meta {
  color: var(--text-primary);
  font-size: 16px;
}

/* These two are hardcoded rather than reading a --text-* token, so they
   need their own override to scale down alongside everything else between
   1200 and 1535px (see base/variables.css for the token-level scaling). */
@media (min-width: 1200px) and (max-width: 1535.98px) {
  .plx-wizard-panel-title,
  .plx-wizard-panel-meta {
    font-size: 15px;
  }
  .plx-room-number-grid {

    grid-template-columns: repeat(auto-fill, minmax(77px, 1fr));
}
}
@media (min-width: 1536px) and (max-width: 1919.98px) {

  .plx-room-number-grid {

    grid-template-columns: repeat(auto-fill, minmax(97px, 1fr));
}
}
@media (min-width: 1920px) {

  .plx-room-number-grid {

    grid-template-columns: repeat(auto-fill, minmax(127px, 1fr));
}
}

.plx-wizard-panel-body {
  display: flex;
  flex-direction: column;
  gap: 15px;
  padding: 15px 25px 0;
}

.plx-wizard-footer {
  align-items: center;
  justify-content: end;
  display: flex;
  /* justify-content: space-between; */
  padding: 15px 25px 20px;
  gap: 10px;
}

/* The Back/Continue pair is wide enough (the longest label is "Continue to
   Property Details") that side-by-side stops fitting once the viewport
   drops below ~400px. Stack them full-width a comfortable margin before
   that, at the same breakpoint already used elsewhere in this file. */
@media (max-width: 575.98px) {
  .plx-wizard-footer {
    flex-direction: column;
    gap: var(--space-3);
    padding: 15px 20px 30px;
  }

  .plx-wizard-footer .plx-btn {
    width: 100%;
  }
}

/* Step 2 — State field: read-only text input (city-derived, see
   CITY_STATE_MAP in property-wizard.js) with a trailing clear button —
   same wrapper/trailing-button positioning as components/forms.css'
   .plx-password-input/.plx-password-toggle-btn (right: var(--space-3),
   24x24px, vertically centered), just re-scoped to this one field since
   it's the only place it's used today. The input itself is plain
   .plx-input, so its background/border/radius match every other field
   here unchanged — only `readonly` blocks typing, not the [disabled]
   muted-background rule. */
.plx-state-input {
  position: relative;
}

.plx-state-input .plx-input {
  padding-right: 44px;
}

.plx-state-clear-btn {
  align-items: center;
  background: none;
  border: 0;
  color: var(--text-muted);
  cursor: pointer;
  display: inline-flex;
  height: 24px;
  justify-content: center;
  padding: 0;
  position: absolute;
  right: var(--space-3);
  top: 50%;
  transform: translateY(-50%);
  width: 24px;
}

.plx-state-clear-btn:hover {
  color: var(--text-primary);
}

/* Step 2 — "Auto-filled based on location" note + live clock below the
   TimeZone field (see resources/views/properties/partials/_wizard_step2.blade.php
   and components/timezone-clock.js). */
.plx-timezone-autofill-note {
  align-items: center;
  color: var(--color-success);
  display: flex;
  font-size: var(--text-sm);
  gap: var(--space-1);
  margin: 0 0 var(--space-2);
}

.plx-timezone-autofill-note .plx-icon {
  color: var(--color-success);
}

/* Outlined only (no fill) — border-default is the same color every
   .plx-input/.plx-select/.plx-textarea already borders itself with, so this
   stays visually tied to the field above it in both light and dark mode. */
.plx-timezone-clock {
  align-items: center;
  background: transparent;
  border: 1.5px solid var(--border-default);
  border-radius: var(--radius-sm);
  color: var(--color-booked);
  display: flex;
  font-size: var(--text-base);
  font-weight: var(--weight-medium);
  gap: var(--space-2);
  min-height: 38px;
  padding: var(--space-2) var(--space-3);
}

.plx-timezone-clock .plx-icon {
  flex-shrink: 0;
  color: var(--pm-accent);
}

/* No nowrap/ellipsis — the full "HH:MM:SS · Weekday, DD Mon YYYY (Zone)"
   string is long enough to need 2 lines on a narrow phone, and wrapping
   keeps every part of it (especially the zone name) readable instead of
   clipping it. */
.plx-timezone-clock-text {
  word-break: break-word;
}

/* "Number of Floors" hidden for the flat unit types (House / Villa,
   Residential Unit, Commercial Unit — see property-wizard.js). Desktop
   (>=768px, .plx-form-row is a row): visibility:hidden keeps this field's
   flex slot reserved so Time Zone stays at the same 50% width as every
   other half-row field instead of stretching to fill the row. Mobile
   (<768px, .plx-form-row stacks into a column — see forms.css): switch to
   display:none instead, since there's no sibling-width relationship to
   preserve there — staying in flow would just leave an empty gap in the
   stacked column. */
.plx-floors-count-group-hidden {
  visibility: hidden;
}

@media (max-width: 767.98px) {
  .plx-floors-count-group-hidden {
    display: none;
  }
}

/* Step 1 — property type grid */
.plx-type-card-grid {
  display: grid;
  gap: 15px 25px;
  grid-template-columns: repeat(3, 1fr);
}

@media (max-width: 991.98px) {
  .plx-type-card-grid {
    grid-template-columns: repeat(2, 1fr);
  }
}

@media (max-width: 575.98px) {
  .plx-type-card-grid {
    grid-template-columns: 1fr;
  }
}

#plxFloorsContainerJs,
#plxUnitFloorsContainerJs,
#plxRoomNumbersContainerJs {
  display: flex;
  flex-direction: column;
  gap: 20px;
}

/* Create-property wizard — floor card (room and unit configuration).
   .plx-flat-units-card-js (House / Villa, Residential Unit, Commercial
   Unit — see _wizard_step3_units.blade.php) shares this exact treatment
   so it visually matches .plx-floor-card-js, just without a "Floor N"
   title since its rows each carry their own Floor Level field instead. */
.plx-floor-card-js,
.plx-flat-units-card-js {
  background: var(--bg-card);
  border-color: var(--border-default);
  border-radius: var(--radius-md);
  border-width: 1px;
  padding: 15px 20px;
}

.plx-floor-card-js .plx-floor-card-header {
  margin-bottom: 0;
  min-height: 45px;
}

.plx-floor-card-js .plx-room-types-js,
.plx-floor-card-js .plx-units-js {
  display: flex;
  flex-direction: column;
  gap: var(--space-3);
  margin-top: 15px;
}

/* Each room-type or unit row is its own white card inside the floor card.
   Covers: Hotel/Motel & Resort (room-type rows), Residential Building (unit
   rows grouped by floor), and House/Villa / Residential Unit / Commercial
   Unit (flat unit rows). Scoped so the shared .plx-config-row base class
   used elsewhere is unaffected. */
.plx-floor-card-js .plx-room-types-js .plx-room-type-row-js,
.plx-floor-card-js .plx-units-js .plx-unit-row-js,
.plx-flat-units-card-js .plx-flat-units-js .plx-unit-row-js {
  background: var(--bg-surface);
  border: 1px solid var(--border-default);
  padding: var(--space-4) var(--space-5);
  border-radius: var(--radius-md);
  -webkit-border-radius: var(--radius-md);
  -moz-border-radius: var(--radius-md);
  -ms-border-radius: var(--radius-md);
  -o-border-radius: var(--radius-md);
}

/* Flat unit-row list — same row stacking as .plx-floor-card-js .plx-units-js
   above, just without the margin-top (no title/header sits above it here,
   since this row list starts right at the top of the card). */
.plx-flat-units-js {
  display: flex;
  flex-direction: column;
  gap: var(--space-3);
}

/* The Add Unit action's divider — same accent-tinted border the floor-card
   header uses above its rows, just on the opposite edge since this layout
   has no title to put a header row above the rows in the first place. */
.plx-flat-units-card-footer {
  align-items: center;
  /* border-top: 1px solid rgb(from var(--pm-accent) r g b / 0.5); */
  display: flex;
  flex-wrap: wrap;
  gap: 10px;
  justify-content: space-between;
  margin-top: 15px;
  padding-top: 16px;
}

/* House / Villa hides the Add Unit button (a house/villa is one single
   property, never a second unit to add — see hideAddUnitCta in
   property-wizard.js). space-between then has only one visible child left
   (.plx-flat-units-card-footer-buttons), which it would push to the start
   instead of its usual end position — keep it right-aligned instead so
   removing the CTA leaves no gap or shifted layout. */
.plx-flat-units-card-footer:has(.plx-add-flat-unit-btn-js.d-none) {
  justify-content: flex-end;
}

/* Back/Create Property move into this row (see syncFooterButtonsPlacement()
   in property-wizard.js) only while step 3 is showing one of the flat unit
   types — grouped together on the right so Add Unit stays the sole item on
   the left, same gap as the buttons already use in .plx-wizard-footer. */
.plx-flat-units-card-footer-buttons {
  align-items: center;
  display: flex;
  gap: 10px;
}

@media (max-width: 575.98px) {
  .plx-flat-units-card-footer {
    flex-direction: column;
  }

  .plx-flat-units-card-footer-buttons {
    flex-direction: column;
    width: 100%;
  }

  .plx-flat-units-card-footer-buttons .plx-btn {
    width: 100%;
  }
}

/* Back/Create Property live inside this card now (see
   syncFooterButtonsPlacement() in property-wizard.js), so the standalone
   .plx-wizard-footer below — which used to be what gave this area its
   bottom breathing room — stays hidden here. Without its own bottom
   margin the card would otherwise sit flush against .plx-wizard-panel-body's
   bottom edge (that panel has no bottom padding of its own; every other
   step relies on the footer below it for this same breathing room). */
#plxFlatUnitsCardJs {
  margin-bottom: var(--space-6);
}

/* Room Category / Room Sub Category / No. of Rooms / Standard Rate fields
   inside the Hotel-Motel "Floors & Room Configuration" row (and the
   matching Unit No. / No. of Rooms / Unit Size / UOM / Rate fields
   inside "Floors & Units Configuration") carry an accent border in the
   Figma source (distinct from the default form-field border used
   elsewhere, e.g. step 2). */
.plx-rt-category-js,
.plx-rt-subcategory-js,
.plx-rt-count-js,
.plx-rt-rate-js,
.plx-unit-no-js,
.plx-unit-rooms-js,
.plx-unit-size-js,
.plx-unit-size-unit-js,
.plx-unit-rate-month-js,
.plx-unit-rate-night-js,
.plx-unit-floor-js {
  border-color: var(--border-focus);
}

/* "+ Add Room Type" pill button (Hotel/Motel "Floors & Room Configuration"
   floor card): white fill, default-gray 1px border, full pill radius,
   muted 14px regular label — matches the Figma component exactly.
   .plx-add-flat-unit-btn-js (House / Villa, Residential Unit, Commercial
   Unit — see _wizard_step3_units.blade.php) shares this exact treatment. */
.plx-add-room-type-btn-js,
.plx-add-unit-btn-js,
.plx-add-flat-unit-btn-js {
  background: var(--bg-surface);
  border-color: var(--border-default);
  border-radius: var(--radius-sm);
  color: var(--text-muted);
  font-size: var(--text-base);
  font-weight: var(--weight-regular);
  height: 30px;
  padding: 0 10px;
}

.plx-add-room-type-btn-js:hover:not(:disabled),
.plx-add-unit-btn-js:hover:not(:disabled),
.plx-add-flat-unit-btn-js:hover:not(:disabled) {
  background: var(--bg-hover);
  border-color: var(--border-default);
  color: var(--text-primary);
}

.plx-add-room-type-btn-js:focus-visible,
.plx-add-unit-btn-js:focus-visible,
.plx-add-flat-unit-btn-js:focus-visible {
  outline: 2px solid var(--outline-focus);
  outline-offset: 2px;
}

.plx-add-room-type-btn-js .plx-icon,
.plx-add-unit-btn-js .plx-icon,
.plx-add-flat-unit-btn-js .plx-icon {
  font-size: 15px;
}

/* Floor/room-type and floor/unit config rows */
.plx-config-row {
  align-items: end;
  display: grid;
  gap: 25px;
}

.plx-config-row > div {
  display: flex;
  flex-direction: column;
  gap: 5px;
}

.plx-config-row-4 {
  grid-template-columns: repeat(4, 1fr) 24px;
}

.plx-config-row-6 {
  grid-template-columns: repeat(6, 1fr) 24px;
}

/* Flat unit-row layout (House / Villa, Residential Unit, Commercial Unit —
   see property-wizard.js' UNIT_TYPE_CONFIG) — same 6 fields as
   .plx-config-row-6 plus its own Floor Level field, since these types skip
   the floor-card grouping entirely. */
.plx-config-row-7 {
  grid-template-columns: repeat(7, 1fr) 24px;
}

/* House / Villa's row has no remove button at all (a house/villa is one
   single property — see hideRemoveUnitCta in property-wizard.js, which is
   what adds this class). Drops the dedicated 24px button track above so no
   empty gap is left in its place; the <1200px breakpoints already share
   the button's column with the last field instead of owning a track, so
   they need no equivalent override. */
.plx-config-row-7.plx-unit-row-no-remove-js {
  grid-template-columns: repeat(7, 1fr);
}

.plx-config-row-remove {
  align-items: center;
  background: transparent;
  border: 0;
  color: var(--color-danger);
  cursor: pointer;
  display: flex;
  height: 38px;
  justify-content: center;
  width: 24px;
}

/* Below 1200px the 6-field unit row (Unit No. / Rooms / Size / UOM /
   Rate-Month / Rate-Night) gets cramped before the 4-field room row does —
   relieve it a breakpoint earlier.

   At each step the row drops its dedicated 24px remove-button track, so the
   button becomes just another grid item — left to auto-placement, it would
   get slotted into whichever column happens to be free on the row it lands
   on (visibly squeezing a field into a narrow cell instead). Pinning it with
   `grid-column: -1` looks tempting but is wrong here: with fewer explicit
   columns than the previous breakpoint, `-1` resolves *past* the explicit
   grid and forces the browser to fabricate an extra implicit column sized
   to the button — which then bleeds into the other rows too and quietly
   turns "1 column" back into two. Targeting the exact last explicit column
   number avoids that. */
@media (max-width: 1199.98px) {
  .plx-config-row-6 {
    grid-template-columns: repeat(3, 1fr);
  }

  .plx-config-row-6 .plx-config-row-remove {
    grid-column: 3;
    justify-self: end;
  }

  .plx-config-row-7 {
    grid-template-columns: repeat(4, 1fr);
  }

  .plx-config-row-7 .plx-config-row-remove {
    grid-column: 4;
    justify-self: end;
  }
}

@media (max-width: 991.98px) {
  .plx-config-row-4,
  .plx-config-row-6,
  .plx-config-row-7 {
    grid-template-columns: repeat(2, 1fr);
  }

  .plx-config-row-4 .plx-config-row-remove,
  .plx-config-row-6 .plx-config-row-remove,
  .plx-config-row-7 .plx-config-row-remove {
    grid-column: 2;
    justify-self: end;
  }
}

@media (max-width: 575.98px) {
  .plx-config-row-4,
  .plx-config-row-6,
  .plx-config-row-7 {
    grid-template-columns: 1fr;
  }

  .plx-config-row-4 .plx-config-row-remove,
  .plx-config-row-6 .plx-config-row-remove,
  .plx-config-row-7 .plx-config-row-remove {
    grid-column: 1;
    justify-self: end;
  }
}

/* Create-property wizard — room number assignment (step 4, Hotel/Motel & Resort) */
.plx-rnf-card-js {
  background: var(--bg-card);
  border-color: var(--border-default);
  border-radius: var(--radius-md);
  border-width: 1px;
  display: flex;
  flex-direction: column;
  gap: var(--space-4);
  padding: var(--space-3) 0 var(--space-6);
}

.plx-rnf-card-js .plx-rnf-title-js {
  color: var(--pm-primary);
  padding: 0 var(--space-5) var(--space-3);
}

.plx-rnf-groups-js {
  display: flex;
  flex-direction: column;
  gap: var(--space-4);
  margin-top: var(--space-4);
}

/* Each room-type group is its own white card inside the floor card */
.plx-room-number-group-js {
  background: var(--bg-surface);
  border: 1px solid var(--border-default);
  border-radius: var(--radius-md);
  padding: var(--space-4);
}

.plx-room-number-group-header {
  align-items: center;
  border-bottom: 1px solid var(--border-default);
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-2);
  justify-content: space-between;
  margin-bottom: var(--space-4);
  padding-bottom: var(--space-4);
}

.plx-room-number-group-header .plx-rng-title-js {
  color: var(--text-secondary);
  flex: 1 1 auto;
  font-size: var(--text-base);
  font-weight: var(--weight-semibold);
  min-width: 0;
}

.plx-room-number-group-header .plx-rng-count-js {
  color: var(--pm-accent);
  flex-shrink: 0;
  font-size: var(--text-base);
  font-weight: var(--weight-semibold);
  margin-left: auto;
  white-space: nowrap;
}

.plx-rng-rate-js {
  color: var(--color-info);
}

.plx-room-number-input {
  border-color: var(--border-default);
  border-width: 1px;
  color: var(--text-secondary);
  font-size: var(--text-xs);
  font-weight: var(--weight-semibold);
  height: 35px;
  text-align: center;
}

.plx-room-number-input:focus {
  border-color: var(--border-focus);
  box-shadow: var(--shadow-focus);
  outline: none;
  border-width: 2px;
}

/* Frame 251.png demo seed rooms (ROOM_NUMBER_SEEDS in property-wizard.js —
   both the pre-filled ones and the still-open trailing ones, e.g. Room
   17-20 / Room 11-15) share this class. The muted fill — the same token
   the global .plx-input:disabled rule reads (components/forms.css), minus
   `cursor: not-allowed` and minus [disabled], since these stay genuinely
   clickable/focusable/editable — only applies while the field is actually
   empty (:placeholder-shown). A field holding its auto-filled value reads
   the base .plx-input white background instead; clearing it (or clearing
   any manually-typed value) empties it again and the muted fill returns —
   so "auto-filled" reads white and "empty" reads muted with no JS needed
   to track which is which. */
.plx-room-number-input.plx-room-number-input-muted-js:placeholder-shown {
  background: var(--bg-surface-muted);
}

.plx-room-number-input::placeholder {
  color: var(--text-subtle);
  font-weight: var(--weight-regular);
}

/* ── Step 4 — Auto Fill (Frame 251.png / auto-fill-range.png) ── */

/* Secondary button chrome, with the reference's gray border instead of the
   lavender --pm-accent-soft, and a nudge of extra space before the room
   count so the button-to-count gap matches the design. */
.plx-rng-autofill-btn-js {
  border-color: var(--border-subtle);
  margin-right: var(--space-1);
}

.plx-autofill-modal-dialog {
  max-width: 500px;
}

/* The reference has no footer divider and pill-shaped action buttons. */
.plx-autofill-modal-dialog .modal-footer {
  border-top: 0;
  padding-top: var(--space-2);
}

.plx-autofill-helper {
  color: var(--text-muted);
  font-size: var(--text-base);
  margin: var(--space-4) 0 0;
}

/* Floor-column rowspan merge (property-detail-unit.js, shared across every
   /properties/{id}/unit page) — same color/thickness as the table's own
   row dividers (.plx-table tbody td's border-bottom in tables.css), just
   on the right edge instead. [rowspan] only ever matches the merged
   cell's own <td>, and only while the JS merge has actually set that
   attribute, so a row with no merge (or no longer merged after a
   sort/filter change) never gets a stray border. */
#plxUnitsTableJs td[rowspan],
#plxRoomsTableJs td[rowspan] {
  border-right: 1px solid var(--border-default);
}

/* ── Rooms/Units tables (Frame 28.png) — every table opened from
   /properties/manage → Manage: the Rooms tab (#plxRoomsTableJs) and each
   unit page's Units tab (#plxUnitsTableJs).
   Header: --bg-thead band with primary-ink labels; all table rules go
   neutral. Column boundaries get inset vertical dividers (equal top/bottom
   spacing) on every th/td except each row's last cell; the rowspan-merged
   Floor cell keeps its full-height right border (rule above) instead.
   Dividers draw on ::before — DataTables' sort arrows own th::after
   (tables.css). ── */
#plxRoomsTableJs thead th,
#plxUnitsTableJs thead th {
  background: var(--bg-thead);
  border-bottom-color: var(--border-default);
  color: var(--pm-primary);
  position: relative;
}

#plxRoomsTableJs tbody td,
#plxUnitsTableJs tbody td {
  border-bottom-color: var(--border-default);
  position: relative;
}

#plxRoomsTableJs thead th:not(:last-child)::before,
#plxRoomsTableJs tbody td:not(:last-child):not([rowspan])::before,
#plxUnitsTableJs thead th:not(:last-child)::before,
#plxUnitsTableJs tbody td:not(:last-child):not([rowspan])::before {
  background: var(--border-default);
  bottom: var(--space-2);
  content: '';
  position: absolute;
  right: 0;
  top: var(--space-2);
  width: 1px;
}

/* Container chrome around these tables only — neutral border per the
   reference instead of the default lavender card border, for both the
   card outline and the card-header underline. */
.plx-card:has(#plxRoomsTableJs),
.plx-card:has(#plxUnitsTableJs) {
  border-color: var(--border-default);
}

.plx-card:has(#plxRoomsTableJs) .plx-card-header.br-btm-clr,
.plx-card:has(#plxUnitsTableJs) .plx-card-header.br-btm-clr {
  border-color: var(--border-default);
}

/* ── /properties/manage — property card view ─────────────────────────
   Cards are plain <div> elements rendered directly in the Blade template.
   properties.js handles search, dropdown filters, pagination, and status
   toggles — no DataTables or jQuery on this page.
   ──────────────────────────────────────────────────────────────────── */

/* ── Card grid container ── */
.plx-property-cards-grid {
  display: grid;
  gap: var(--space-5);
  grid-template-columns: repeat(3, 1fr);
}

/* ── Individual property card ── */
.plx-property-card {
  background: var(--bg-surface);
  border: 1px solid var(--border-default);
  border-radius: var(--radius-md);
  box-shadow: var(--shadow-card-hover);
  display: flex;
  flex-direction: column;
  overflow: hidden;
  transition: border-color var(--transition-fast), box-shadow var(--transition-fast);
}
:root[data-bs-theme="dark"] .plx-property-card:hover {
  box-shadow: var(--shadow-md);
}

.plx-property-card:hover {
  border-color: var(--border-hover);
}

.plx-property-card:active {
  box-shadow: var(--shadow-card-hover);
}

/* ── Card header: inline ID badge + property name ── */
.plx-property-card-header {
  align-items: center;
  display: flex;
  gap: var(--space-3);
  min-height: 56px;
  padding: 0 var(--space-4);
  background: var(--bg-hover);
}

/* ID badge: small lavender box with full border and rounded corners */
.plx-property-card-id {
  --property-card-id-size: 28px;
  align-items: center;
  background: var(--bg-surface);
  border: 1px solid var(--border-default);
  border-radius: var(--radius-sm);
  color: var(--pm-primary);
  display: inline-flex;
  flex: 0 0 auto;
  font-size: var(--text-sm);
  font-weight: var(--weight-semibold);
  height: var(--property-card-id-size);
  justify-content: center;
  line-height: 1;
  min-width: var(--property-card-id-size);
  padding: 0 var(--space-2);
}

/* Property name */
.plx-property-card-name {
  color: var(--text-primary);
  flex: 1;
  font-size: var(--text-base);
  font-weight: var(--weight-semibold);
  line-height: 1.3;
  min-width: 0;
}

/* ── Card body: key-value rows ── */
.plx-property-card-body {
  display: flex;
  flex-direction: column;
}

/* Two-column grid. border-top on every row creates the header→row separator
   (first row) and all row→row separators (subsequent rows) without needing
   a separate border on the header or body wrapper. */
/* Spacing lives on the label/value cells, not the row — same pattern as
   .plx-allotment-card-row / .plx-allotment-card-field in operations.css.
   The label column is widened by the label's own left padding so the value
   column (and the divider on its left edge) stays at the exact x it had
   when the row carried the padding. */
.plx-property-card-row {
  --property-card-label-w: 140px;
  align-items: center;
  border-top: 1px solid var(--border-default);
  display: grid;
  grid-template-columns: calc(var(--property-card-label-w) + var(--space-4)) 1fr;
  min-height: 44px;
  position: relative;
}

/* font-size stays a literal 14px on purpose: --text-base drops to 13px in
   the 1200–1535px window (base/variables.css), and these cards keep their
   14px text at every width — same reasoning as .plx-wizard-panel-title
   above. */
.plx-property-card-label {
  color: var(--text-muted);
  font-size: 14px;
  font-weight: var(--weight-regular);
  line-height: 1.4;
  padding: 10px 10px 10px var(--space-4);
}

.plx-property-card-value {
  color: var(--text-secondary);
  font-size: 14px;
  font-weight: var(--weight-semibold);
  line-height: 1.4;
  padding: 10px var(--space-4) 10px 10px;
  position: relative;
  word-break: break-word;
}

/* Column divider before the value — same inset-divider implementation as
   .plx-allotment-card-field::before in operations.css. Anchored to the row
   (the value span is center-aligned and only as tall as its text), with no
   `left` so the static position pins it to the value column's start —
   it tracks --property-card-label-w automatically. */
.plx-property-card-value::before {
  background: var(--border-default);
  bottom: var(--space-3);
  content: '';
  position: absolute;
  top: var(--space-3);
  width: 1px;
  left: 0;
}

/* ── Card footer: status toggle + action button ── */
.plx-property-card-footer {
  align-items: center;
  border-top: 1px solid var(--border-default);
  display: flex;
  justify-content: space-between;
  margin-top: auto;
  padding: var(--space-4) var(--space-4);
}

/* Manage button — taller than the default 30px, with wider padding.
   The !important guards against buttons.css shrinking it to 24px at
   1200–1536px (`.plx-view-btn { height: 24px }` media query).
   Colors match .plx-btn-primary (buttons.css) — same tokens for
   background, border, and text, including the hover state. */
.plx-property-card-footer .plx-view-btn {
  background: var(--pm-primary);
  border-color: var(--pm-accent-soft);
  color: var(--text-inverse);
  height: 36px;
  padding: 0 var(--space-4);
}

.plx-property-card-footer .plx-view-btn:hover {
  background: var(--pm-primary-hover);
  border-color: var(--pm-primary-hover);
  color: var(--text-inverse);
}

/* Empty state message. font-size: see the note on .plx-property-card-label. */
.plx-cards-empty {
  color: var(--text-muted);
  font-size: 14px;
  padding: var(--space-12) var(--space-4);
  text-align: center;
}

/* ── Responsive breakpoints ── */

@media (max-width: 1199.98px) {
  .plx-property-cards-grid {
    grid-template-columns: repeat(2, 1fr);
  }
}

@media (max-width: 767.98px) {
  .plx-property-cards-grid {
    gap: var(--space-3);
    grid-template-columns: 1fr;
  }
}

/* ── Add Room(s) modal — Room Type rows ──────────────────────────────────
   resources/views/properties/partials/_room_modals.blade.php */

.plx-room-type-rows {
  display: flex;
  flex-direction: column;
  gap: var(--space-4);
  margin-bottom: var(--space-4);
}

.plx-room-type-row {
  background: var(--bg-surface-muted);
  border: 1px solid var(--border-default);
  border-radius: var(--radius-sm);
  padding: var(--space-4);
}

.plx-room-type-row-header {
  align-items: center;
  display: flex;
  justify-content: space-between;
  margin-bottom: var(--space-3);
}

.plx-room-type-row-title {
  color: var(--text-muted);
  font-size: var(--text-sm);
  font-weight: var(--weight-medium);
}

.plx-room-type-row-remove {
  align-items: center;
  background: none;
  border: 0;
  border-radius: var(--radius-sm);
  color: var(--color-danger);
  cursor: pointer;
  display: inline-flex;
  height: 24px;
  justify-content: center;
  padding: 0;
  transition: background-color var(--transition-fast);
  width: 24px;
}

.plx-room-type-row-remove:hover {
  background: var(--color-danger-bg);
}

/* 4-up: Room Category / Room Sub Category / No. of Rooms / Standard
   Rate/Night. Each row's own fields, not the shared .plx-form-row (that
   one assumes 2-3 equal-width children with a wider 60px gap tuned for
   that count — cramped and oversized at 4 across). */
.plx-room-type-row-fields {
  display: grid;
  gap: var(--space-4);
  grid-template-columns: repeat(4, 1fr);
}

.plx-room-type-row-fields .plx-form-group {
  margin-bottom: 0;
}

/* Smaller than the project-wide .plx-label (--text-md) — 4 labels across
   this row need to stay a comfortable one-liner without pushing the modal
   even wider than the 760px it already needed for this. Scoped to just
   these rows' own labels, not a global .plx-label change. */
.plx-room-type-row-fields .plx-label {
  font-size: var(--text-sm);
}

.plx-add-room-type-btn {
  margin-bottom: var(--space-4);
}

@media (max-width: 767.98px) {
  .plx-room-type-row-fields {
    grid-template-columns: 1fr 1fr;
  }
}

@media (max-width: 575.98px) {
  .plx-room-type-row-fields {
    grid-template-columns: 1fr;
  }
}