The following event descriptions on your website are very confusing to me
checkout-submit: Called when the checkout is submitted
checkout-submit-enable: Triggered when the checkout button is set to enabled (when all fields are completed and errors are handled).
checkout-submit-disable: Called when checkout button is disabled due to errors
particulary the enable and disable. to me it reads like enable is called if there are no errors, and disable is called if there are errors, when it does not appear this is the case...the checkout-submit-disable event is always called first out of these three, just after the submit button is disabled after being clicked (irregardless of whether or not there are errors on the form), next checkout-submit is called, and then assuming the form could not be submit, checkout-submit-enable is called (ONLY if there are checkout errors), right after the submit button is re-enabled so the user can correct and attempt a re-submit.
is this accurate? its important to me because I'd like to know the best way to determine if a form has errors or not when the submit button is clicked.
I'd also love to know how i might disable the form button completely until the form is free of errors, and only then enable it, this seems nicer than allowing it to be clickable, only to find out I missed a requirement.