**Motivation**
When the confirmation prompt is added through javascript, it is possible that the page has loaded, but the confirmation prompt logic has not. If that is the case, it should still not be possible to accidentally rollback without confirmation
**User Story**
As an editor with enabled rollback confirmation prompt
I want to be sure I am always asked for confirmation
so that I don't ever have to fear misclicks when it comes to rollbacks
**Acceptance Criteria**
[] It should never be humanly possible to trigger a rollback action without previously having seen the confirmation prompt (if that is the user setting). It would both be ok if
- the user saw a non-js page for confirmation purposes instead
- the user's click was "delayed" for a bit