/**
 * /my-sessions/login - what is this page's alone.
 *
 * The frame, the card, the fields and the button are the shared ones
 * (rba-sessions.page.css); this page only has to place a Drupal-rendered form
 * inside them. Drupal wraps each element in its own .form-item markup, so the
 * few bits of glue that maps onto live here rather than in the shared file.
 */

/* One field per row, label above input, matching .rba-sessions-form's rhythm. */
.rba-sessions-login__form .form-item {
  margin: 0 0 var(--spacing-200, 16px);
}

.rba-sessions-login__form .form-item > label {
  display: block;
  margin-bottom: var(--spacing-050, 4px);
  font-size: var(--text-paragraph-s, 15px);
  font-weight: var(--font-weight-bold, 700);
}

/* Drupal marks a required field with a <span class="form-required"> the theme
   renders as an asterisk; nothing to add here beyond keeping it in the
   sentence colour rather than the browser's red. */
.rba-sessions-login__form .form-required::after {
  color: var(--accent, #fa263a);
}

.rba-sessions-login__form .form-actions {
  margin: var(--spacing-300, 24px) 0 0;
  text-align: center;
}

/* The confirmation after a submission is left to the theme's message region,
   where every other form on the site puts it - see AttendeeLoginRequestForm for
   why it is not rendered into the card instead.
   */

/* Honeypot: off-screen rather than display:none/visibility:hidden, which some
   bots explicitly check for and skip filling. */
.rba-login-honeypot {
  position: absolute;
  left: -9999px;
  width: 1px;
  height: 1px;
  overflow: hidden;
}