views/CreateTicketView.php (~line 347) uses the native browser confirm() dialog to warn before a template overwrites in-progress title/description text. This directly violates README.md Developer Notes #21: "Never use browser confirm(). Use showConfirmModal(title, message, type, onConfirm)." Every other confirm-before-destructive-action flow in the app (delete field, delete transition, delete template, revoke key, etc.) correctly uses the styled showConfirmModal() — this is the one inconsistent spot, and also the one place where a template swap could silently blow away typed content if the browser's native dialog styling confuses a user into missing/dismissing it incorrectly.
Fix: Replace the confirm() call with showConfirmModal(...), matching every other destructive-action confirmation in the app.
**Severity:** Low (consistency / documented-convention violation)
`views/CreateTicketView.php` (~line 347) uses the native browser `confirm()` dialog to warn before a template overwrites in-progress title/description text. This directly violates README.md Developer Notes #21: "Never use browser `confirm()`. Use `showConfirmModal(title, message, type, onConfirm)`." Every other confirm-before-destructive-action flow in the app (delete field, delete transition, delete template, revoke key, etc.) correctly uses the styled `showConfirmModal()` — this is the one inconsistent spot, and also the one place where a template swap could silently blow away typed content if the browser's native dialog styling confuses a user into missing/dismissing it incorrectly.
**Fix:** Replace the `confirm()` call with `showConfirmModal(...)`, matching every other destructive-action confirmation in the app.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: Low (consistency / documented-convention violation)
views/CreateTicketView.php(~line 347) uses the native browserconfirm()dialog to warn before a template overwrites in-progress title/description text. This directly violates README.md Developer Notes #21: "Never use browserconfirm(). UseshowConfirmModal(title, message, type, onConfirm)." Every other confirm-before-destructive-action flow in the app (delete field, delete transition, delete template, revoke key, etc.) correctly uses the styledshowConfirmModal()— this is the one inconsistent spot, and also the one place where a template swap could silently blow away typed content if the browser's native dialog styling confuses a user into missing/dismissing it incorrectly.Fix: Replace the
confirm()call withshowConfirmModal(...), matching every other destructive-action confirmation in the app.