/*!******************************************************************************************************************!*\
  !*** css ./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[0].use[1]!./Content/Styles/formSubmitGuard.css ***!
  \******************************************************************************************************************/
/* pazar_new.css only styles :disabled under .plan-selection-page, and its base
   `.new-btn` rule hard-sets `opacity: 1`. !important rather than a specificity
   race, matching how the rest of that stylesheet resolves state conflicts. */
form button[type="submit"]:disabled,
form input[type="submit"]:disabled,
form button[type="submit"][disabled],
form input[type="submit"][disabled],
form button[type="submit"].is-submitting,
form input[type="submit"].is-submitting {
    opacity: 0.4 !important;
    filter: grayscale(35%) !important;
    cursor: not-allowed !important;
}

/* No pointer-events:none on buttons. It removes them from hit-testing, so a press
   that starts while the button is still disabled lands on the form instead and the
   release never completes a click on the button - which reads as "I had to click
   twice". `disabled` already blocks activation on its own. Anchors are different:
   they have no disabled state, so the link genuinely needs it. */
a.disabled {
    opacity: 0.4 !important;
    filter: grayscale(35%) !important;
    cursor: not-allowed !important;
    pointer-events: none !important;
}


/*# sourceMappingURL=formSubmitGuardCss.bundle.css.map*/