Buttons have no ID optionality about alertjs HOT 3 CLOSED

Hi Sven,

Unfortunately we currently don't support disabling the alert buttons. As you mentioned it's technically possible with something like this: Alert.$("button:contains('OK')").prop("disabled", true) but there's no guarantee that the buttons will still be buttons in the future etc, so do this at your own risk.

The way we usually recommend adding validation is to keep the buttons clickable, but add the validation on click. If some input on the popup is invalid then you can display the error message to the user and prevent the button action. Note that you can use the preventClose property on the button object to keep the alert open so you can run validation, then manually close it with Alert.hide(); when the validation is successful.

You may also want to consider upgrading to v3.0 as the support for Alert.$ and nested alerts are only in 3.0.

Cheers,
Paul

from alertjs.

Hi Paul,

Thanks for the quick Response.

At the Moment we have fixed it by keeping the custom Buttons (with Code) in the HTML itself and not defining them in the constructor. Afterwards we then close the Dialog ourselves.

I only made this Issue, due to that it actually feels like this is a missing feature in the great product you provide and which could Maybe eaily be implemented in the button constructor?

Anyway, I thank you once more for the quick Response and the great product you provide.

Regards,
Sven

from alertjs.

Hi Sven,

Appreciate the feedback, we'll definitely consider d this as a feature in the future, as I agree that it could be useful in certain scenarios such as yours.

Thanks again,
Paul Nieuwelaar

from alertjs.