/* ENVOY — order-submit.css
   the submit button, the status line, errors, confirmation

   One part of a stylesheet split across files. The load order in
   index.html is part of the stylesheet — see css/base.css for the map. */

/* ---- submit, status, errors ---- */

.order-submit {
  width: 100%;
  margin-top: clamp(6px, 1vh, 12px);
  padding: 1em 1.2em;
  border: 1px solid var(--red);
  border-radius: 2px;
  background: var(--red);
  color: #fff;
  font-family: "Courier Prime", "Courier New", monospace;
  font-size: clamp(12px, 1vw, 14px);
  font-weight: 700;
  letter-spacing: 0.24em;
  text-indent: 0.24em;
  text-transform: uppercase;
  cursor: pointer;
  transition: background-color 0.18s ease, border-color 0.18s ease;
}

.order-submit:hover:not(:disabled),
.order-submit:focus-visible:not(:disabled) {
  background: var(--red-bright);
  border-color: var(--red-bright);
}

/* The label changes to "Reserving…" while a submit is in flight, so the
   disabled state only has to say "not now", not explain itself. */
.order-submit:disabled {
  background: rgba(239, 32, 21, 0.3);
  border-color: rgba(239, 32, 21, 0.3);
  color: rgba(255, 255, 255, 0.66);
  cursor: default;
}

/* Empty until the script writes to it. Kept in the flow with no reserved
   height — a permanent blank line under the button reads as a mistake, and
   the box growing by one line on a failed submit is not motion worth
   engineering around. */
.order-status {
  margin: clamp(10px, 1.6vh, 16px) 0 0;
  font-family: "Courier Prime", "Courier New", monospace;
  font-size: clamp(11px, 0.9vw, 13px);
  line-height: 1.45;
  letter-spacing: 0.06em;
  color: rgba(243, 228, 226, 0.66);
}

.order-status.is-bad { color: var(--red-bright); }

.order-error {
  margin: 0.5em 0 0;
  font-family: "Courier Prime", "Courier New", monospace;
  font-size: clamp(10px, 0.85vw, 12px);
  letter-spacing: 0.06em;
  color: var(--red-bright);
}

/* What happens to the address, said next to the box that asks for it rather
   than in a privacy page nobody opens. */
.order-hint {
  margin: 0.55em 0 0;
  font-family: "Cormorant Garamond", "EB Garamond", Garamond, serif;
  font-size: clamp(13px, 1.02vw, 16px);
  line-height: 1.4;
  color: rgba(243, 228, 226, 0.5);
}

/* The one field that is a sentence rather than a box, so it wants the space
   a paragraph would get above it. */
.order-field--check { margin-top: clamp(20px, 3vh, 30px); }

/* Set by js/order.js on the offending control, so the field itself carries
   the error and not only the line under it. */
.order-input[aria-invalid="true"] { border-color: var(--red-bright); }

/* ---- confirmation ---- */

.order-reset {
  margin-top: clamp(16px, 2.4vh, 24px);
  padding: 0.72em 1.1em;
  border: 1px solid rgba(239, 32, 21, 0.55);
  border-radius: 2px;
  background: transparent;
  color: var(--red);
  font-family: "Courier Prime", "Courier New", monospace;
  font-size: clamp(10px, 0.85vw, 12px);
  font-weight: 700;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  cursor: pointer;
  transition: color 0.18s ease, border-color 0.18s ease;
}

.order-reset:hover,
.order-reset:focus-visible {
  color: var(--red-bright);
  border-color: var(--red-bright);
}

/* The panel the fire sinks into, and the foot of the site. Black is simply the
   plate at zero. min-height rather than height: the footer sets the real
   height once it has content, and this only guarantees the fade has a full
   screen to finish into. */
.closing {
  position: relative;
  z-index: 1;
  min-height: 100vh;
  display: flex;
  /* Pinned to the bottom, where it used to be centred. Centring was the right
     call when the wordmark was an inset image floating in the middle of the
     panel — flex-end then left it reading as a strip at the foot of a screen of
     nothing. It is now full-bleed and lands on the document's last row of
     pixels, so the bottom edge is something the composition sits *on* rather
     than drifts near, and the black left above it is the fire's exit rather
     than a hole. */
  align-items: flex-end;
}
