Unify dialogs and confirmations on one native dialog pattern closes #615 #617
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
local-it/mitgliederverwaltung!617
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue/mitgliederverwaltung-615"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of the implemented changes
The changes were:
Dialog and confirmation components: one dialog pattern, one confirmation rule. Every dialog in the app now renders through
<.modal>(a native<dialog>whose close paths all route throughon_cancel) and every confirmation through<.confirm_dialog>, with one rule for when a confirmation is simple and when the user types the name: deleting a member, group, data field or all fee cycles is typed; the rest is a simple confirmation that states the consequence in a warning callout. The server re-checks the permission on the record it holds before deleting,data-confirmand hand-built modal markup are gone (pinned at zero by the UI guard), and the legacy server-pushed focus restore is removed in favour of the dialog's own focus return.What has been changed?
Definition of Done
Code Quality
Accessibility
Testing
Additional Notes
transition: overlay, which Firefox and Safari lack, so the dialog now fades out while still open.role_live_test.exsasync, so the merge commit moves this branch's two log-capturing role tests into the serial modulerole_live_logging_test.exs, as #611 did for its own log tests.