Affected users are still prompted to confirm the rollback as the non-JS rollback confirmation will take over, so this is not a critical issue and users can not accidentally rollback anything, it's mainly a user-experience problem.
The issue itself is kind of related to how the "Confirmables" work that we are using in the code to implement the user confirmation:
As far as I can see, we can either fix this by making changes to the Confirmable script as the issue is strongly linked to it (since we are simply re-using it, much like the Thanks extension). Alternatively, we can also consider this a minor issue and postpone this until a better, more permanent solution is found for the user interface. However, I assume the latter will take too much time, so it may be best to first fix the current approach before we move forward.
A solution may be to implement delegated event handlers into the Confirmable script, but we may need to double-check this.