.gtp-tune-request {
    max-width: 640px;
    margin: 0 auto;
}

.gtp-tune-request fieldset {
    border: 1px solid #ddd;
    border-radius: 4px;
    padding: 1em 1.25em;
    margin-bottom: 1.25em;
}

.gtp-tune-request legend {
    font-weight: 600;
    padding: 0 0.5em;
}

.gtp-field {
    margin-bottom: 1em;
}

.gtp-field label {
    display: block;
    font-weight: 600;
    margin-bottom: 0.25em;
}

.gtp-field input[type="text"],
.gtp-field input[type="email"],
.gtp-field input[type="tel"],
.gtp-field textarea,
.gtp-field select {
    width: 100%;
    box-sizing: border-box;
    padding: 0.5em;
}

.gtp-field.gtp-radio label {
    font-weight: normal;
    display: inline-flex;
    align-items: center;
    gap: 0.5em;
}

.gtp-help {
    display: block;
    color: #666;
    font-size: 0.9em;
    margin-top: 0.25em;
}

.gtp-honeypot {
    position: absolute;
    left: -9999px;
    top: -9999px;
}

.gtp-subfield {
    margin-left: 1.5em;
    margin-bottom: 1em;
}

.gtp-notice {
    /* Deliberately no background/text color here -- this plugin embeds into whatever theme
       hosts it, and a fixed light fill color with no matching text color looks fine on a
       stock light theme but goes near-invisible (white text on a pale fill) on a dark one.
       An outline-only treatment inherits both background and text color from the page
       itself, so it stays readable regardless of the theme. Only the border color signals
       success/error. (The submit button below is a deliberate exception to "inherit
       everything" -- see .gtp-submit-button.)
     */
    padding: 1em;
    border-radius: 4px;
    border: 2px solid;
    margin-bottom: 1em;
}

.gtp-notice p {
    /* Respects line breaks the shop typed into a custom message (e.g. Settings ->
       Customer failure message) without needing real <br> markup. */
    white-space: pre-line;
}

.gtp-notice-success {
    border-color: #34c98d;
}

.gtp-notice-error {
    border-color: #e5534b;
}

.gtp-download-link {
    display: inline-block;
    font-weight: 600;
}

/* Matches the submit button on the site's other request form (EFI Tuning, Fluent Forms) --
   #409EFF is that form's exact button color, kept here so the two forms feel like part of
   the same site rather than one obviously being a different plugin.

   Higher-specificity selector + !important on the color properties specifically: most
   theme stylesheets style `button`/`input[type=submit]` fairly aggressively (often with
   their own !important, since they want one consistent button look site-wide), which a
   plain .gtp-submit-button class selector loses to. This is a deliberate, narrow override
   of that inherited styling for this one button -- everything else in the form still
   inherits the theme as usual. */
.gtp-tune-request form .gtp-submit-button.gtp-submit-button {
    background-color: #409EFF !important;
    color: #ffffff !important;
    border: none;
    border-radius: 4px;
    padding: 0.65em 1.6em;
    font-size: 1em;
    font-weight: 600;
    cursor: pointer;
}

.gtp-tune-request form .gtp-submit-button.gtp-submit-button:hover,
.gtp-tune-request form .gtp-submit-button.gtp-submit-button:focus-visible {
    background-color: #2f8ce6 !important;
}

.gtp-tune-request form .gtp-submit-button.gtp-submit-button:disabled {
    opacity: 0.6;
    cursor: not-allowed;
}

.gtp-spinner {
    margin-left: 0.5em;
    color: #666;
}