When a user clicks the Abort button on a running task, a confirmation button appears immediately below it. This layout makes it easy to accidentally confirm the abort with a second click, potentially interrupting tasks unintentionally.
Proposed solution
The goal is to redesign the abort confirmation flow so that accidental aborts are prevented. This could involve moving the confirmation further away, introducing a modal dialog, requiring an extra interaction step, or any other UX pattern that clearly separates the intent to abort from the confirmation.
All NS8 users who manage long-running tasks benefit from this improvement, especially in high-stakes operations where an accidental abort could cause data loss or require restarting a lengthy process.
Alternative solutions
Keep the current inline confirmation layout.
References
When a user clicks the Abort button on a running task, a confirmation button appears immediately below it. This layout makes it easy to accidentally confirm the abort with a second click, potentially interrupting tasks unintentionally.
Proposed solution
The goal is to redesign the abort confirmation flow so that accidental aborts are prevented. This could involve moving the confirmation further away, introducing a modal dialog, requiring an extra interaction step, or any other UX pattern that clearly separates the intent to abort from the confirmation.
All NS8 users who manage long-running tasks benefit from this improvement, especially in high-stakes operations where an accidental abort could cause data loss or require restarting a lengthy process.
Alternative solutions
Keep the current inline confirmation layout.
References