/**
 * Player Identity Screen ("Come si chiama il giocatore?")
 *
 * Reuses Name Entry's own field architecture (.tr-name-entry-group/
 * .tr-name-entry-field, see tr-name-entry.css) for NOME/COGNOME, and
 * TRQuestionCard's own .tr-question-card/.tr-question-card-title.
 * CONTINUA deliberately does NOT reuse .tr-name-entry-continue (that
 * class also carries Name Entry's own screen-specific margin-top
 * override, which this screen never wanted -- see tr-player-identity-
 * section.js's own note) -- it renders through the shared
 * .tr-option-button.tr-primary-action rule alone (tr-question.css),
 * completely unmodified, the same as every other default CONTINUA.
 * The one genuinely new rule this screen needs is the gender row below:
 * .tr-question-card-options (tr-question.css) is a VERTICAL, scrollable
 * option list built for Slide 7's own role picker, wrong for this
 * screen's fixed two-button row, so this screen uses its own row
 * layout instead -- same shape as .tr-dob-row's own two/three equal-
 * width fields (tr-question.css).
 */

/* ---------- Gender row ---------- */
.tr-player-identity-gender-row {
    display: flex;
    /* Same 12px as .tr-question-card's own child gap (tr-question.css,
       the space already separating COGNOME from this row) -- one
       value controls both relationships, not two independent ones. */
    gap: 12px;
}

.tr-player-identity-gender-row .tr-option-button {
    width: auto;
    min-width: 0;
    flex: 1 1 0;
}

/* ---------- Femmina/Maschio states ---------- */
/* Overrides only the shared .tr-option-button's own colors for these
   two buttons -- size/position/spacing/typography (above) and the
   border/radius/background shape itself are untouched. Default and
   UNSELECTED are identical (white outline + white text); SELECTED is
   lime outline + lime text, never the shared --selected rule's own
   lime-FILLED look (tr-question.css) -- so the gender buttons stay
   outline-only in every state, including the momentary :active tap
   state. */
.tr-player-identity-gender-row .tr-option-button,
.tr-player-identity-gender-row .tr-option-button:active {
    background: #000000;
    border-color: #ffffff;
    color: #ffffff;
}

.tr-player-identity-gender-row .tr-option-button--selected,
.tr-player-identity-gender-row .tr-option-button--selected:active {
    background: #000000;
    border-color: var(--tr-color-green);
    color: var(--tr-color-green);
}

/* Confirmation mode only (TROptionButton's own setDisabled(), see
   enterConfirmMode()): the UNSELECTED button additionally dims to 50%
   opacity -- same white outline/text as above, just dimmed, so it
   visually recedes behind the selected one. The SELECTED button stays
   full lime/full opacity (the --selected:disabled rule below has the
   same specificity as this one and wins by coming after it in source
   order). */
.tr-player-identity-gender-row .tr-option-button:disabled {
    background: #000000;
    border-color: #ffffff;
    color: #ffffff;
    opacity: 0.5;
}

.tr-player-identity-gender-row .tr-option-button--selected:disabled {
    background: #000000;
    border-color: var(--tr-color-green);
    color: var(--tr-color-green);
    opacity: 1;
}

/* ---------- Confirmation mode: card + fields ---------- */
/* Added/removed by TRPlayerIdentitySection's own enterConfirmMode()/
   enterEditMode(). Only the border color changes -- .tr-question-
   card's own background (tr-question.css) is untouched, so the card
   stays the same dark/transparent black. --tr-color-accent is the
   exact same lime token .tr-name-entry-field .tr-phone-label already
   reads below (tr-name-entry.css) -- not a new color. */
.tr-player-identity-card--confirm {
    border-color: var(--tr-color-accent);
}

.tr-player-identity-field--confirm {
    border-color: var(--tr-color-accent);
}

/* NOME/COGNOME's own label is already lime at all times (tr-name-
   entry.css); only the VALUE needs to turn lime for this mode (it is
   --tr-color-text-dim, i.e. white, the rest of the time). */
.tr-player-identity-field--confirm .tr-phone-input {
    color: var(--tr-color-accent);
}

/* No EDIT-mode/confirmation-mode CONTINUA color overrides needed here:
   the shared .tr-option-button.tr-primary-action.tr-option-button--
   selected rule (tr-question.css) already renders the fully lime-
   filled/black-text look unconditionally whenever the button is
   filled:true and not :disabled -- true in both this screen's EDIT-
   mode-once-valid state and its confirmation (CONFERMA E CONTINUA)
   state alike, so there is nothing left for this screen to override.
   (Previously this file re-asserted those exact same values through
   .tr-name-entry-continue-scoped rules; removed as redundant once this
   screen stopped reusing that class -- see tr-player-identity-
   section.js's own note.) */
