Hi,
There is no issue with the trigger.
You need to look at the code of the function setLoading in media/com_hikashop/js/checkout.js
You'll see this:
setLoading: function(el, load) {
var w = window, o = w.Oby, t = this, d = document, btn = d.getElementById('hikabtn_checkout_next');
if(el) {
if(load)
o.addClass(el, "hikashop_checkout_loading");
else
o.removeClass(el, "hikashop_checkout_loading");
}
if(load)
t.loading++;
else if(t.loading > 0)
t.loading--;
// we block the next button while blocks are being submitted to avoid wrong actions to be validated while finishing the checkout
if(btn) {
if(t.loading) {
btn.disabled = true;
o.addClass(btn, 'next_button_disabled');
} else {
btn.disabled = false;
o.removeClass(btn, 'next_button_disabled');
}
}
}
As you can see, there is a mechanism to prevent the users from using the next button while blocks are being submitted.
So if the btn.disabled variable is not set back to true, the next button won't work.
In the submitBlock function, there is a call to t.setLoading(el, false); to reset the next button state after an AJAX call so that the next button can be used again after the block is submit.
But I suppose that the code you have somehow skips resetting the state of the next button.