I had filed a couple of separate issues for this back in 2015, about specific pages. Let's make this issue here a meta to list all such issues.
First step would be:
- [ ] #3771 | [UX] Introduce a
confirm_dialog()function (and use that one instead ofconfirm_form())
Specific confirmation pages to be converted to dialogs:
- [ ] #769 | [UX] Move the confirmation dialog for deletion of nodes to a modal.
- [ ] #770 | [UX] Move the confirmation dialog for deletion of menu links to a modal.
- [ ] #3770 | [UX] Move the confirmation dialog for enabling/uninstalling modules to a modal.
Related D8 issues:
- Add abstracted dialog to core (resolves accessibility bug)
- [META] Convert all confirm forms already converted to new routing system to use modal dialog
(Triaged as possible accessibility issue on 08/17/2921. This one may or many not qualify, please add the [A11Y] tag if you think it qualifies.)
GitHub Issue #:
3769
Recent comments
Ruby Text can be a bit of a hassle to edit... Yes, I can imagine that. No idea, how an editor dialog (or whatever) for easier editing of those should look like - in terms of...
Specific tags to work in CKEditor 5
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Specific tags to work in CKEditor 5
Out of curiosity: why are these tags only relevant for admins? Don't "regular" editors on that site also need them under circumstances? Yes, the editors play nicely, no problem to...
Specific tags to work in CKEditor 5