You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maintainer-owned: This issue is intentionally labeled not ready yet. Please leave implementation to a PyRIT maintainer unless a maintainer explicitly assigns or approves the work.
Describe the bug
Choosing Remove on an additional initializer immediately sends the delete request and removes the persisted card. There is no confirmation step, no warning that the action is immediate, and no undo affordance after success.
This makes an easy misclick destructive. The neighboring Edit and Remove actions have similarly direct presentation, but only one changes persisted configuration irreversibly from the page. Severity: moderate because one accidental activation deletes configuration without a recovery path.
Steps/Code to Reproduce
Open the Initializers page in the local frontend.
Add a refresh_datasets initializer with days set to 7.
On the saved initializer card, choose Remove once.
Observe that no confirmation dialog appears.
Observe that the card disappears immediately after the delete succeeds.
Search the resulting page for an Undo action; none is available.
# N/A - GUI-only reproduction; no Python code is required.
Expected Results
Before or immediately after the destructive action, the UI should provide a clear recovery safeguard: either a confirmation that identifies the initializer being removed, or a short-lived undo action that restores it. The exact pattern should be resolved during UX/design triage.
Actual Results
The first Remove activation immediately deletes the initializer. No confirmation, warning, or undo control appears, and restoring the configuration requires manually recreating it.
Screenshots
Sanitized before/after screenshots and WebM evidence, showing only the application viewport and synthetic numeric values, are attached in the evidence comment below.
Important
Maintainer-owned: This issue is intentionally labeled
not ready yet. Please leave implementation to a PyRIT maintainer unless a maintainer explicitly assigns or approves the work.Describe the bug
Choosing Remove on an additional initializer immediately sends the delete request and removes the persisted card. There is no confirmation step, no warning that the action is immediate, and no undo affordance after success.
This makes an easy misclick destructive. The neighboring Edit and Remove actions have similarly direct presentation, but only one changes persisted configuration irreversibly from the page. Severity: moderate because one accidental activation deletes configuration without a recovery path.
Steps/Code to Reproduce
refresh_datasetsinitializer withdaysset to7.# N/A - GUI-only reproduction; no Python code is required.Expected Results
Before or immediately after the destructive action, the UI should provide a clear recovery safeguard: either a confirmation that identifies the initializer being removed, or a short-lived undo action that restores it. The exact pattern should be resolved during UX/design triage.
Actual Results
The first Remove activation immediately deletes the initializer. No confirmation, warning, or undo control appears, and restoring the configuration requires manually recreating it.
Screenshots
Sanitized before/after screenshots and WebM evidence, showing only the application viewport and synthetic numeric values, are attached in the evidence comment below.
Versions
3dd9946ee4ef08a2048c64ff4b29d3a856a8068e@playwright/test1.62.0)pyrit.show_versions(): N/A for this frontend-only reproduction