Data Views: Pages: Improve clarity of the Trash and Permanently delete flows #60383
Labels
[Feature] Site Editor
Related to the overarching Site Editor (formerly "full site editing")
[Focus] Accessibility (a11y)
Changes that impact accessibility and need corresponding review (e.g. markup changes).
Needs Design
Needs design efforts.
[Type] Bug
An existing feature does not function as intended
Description
See previous similar issue #52639
From the Site editor > pages, a page can be 'moved to the trash'. Screenshot:
However, the confirm dialog that opens when trashing a page, asks users whether they want to delete the page. Screenshot:
That's less than ideal. It's confusing for users, as they will not trust the editor and potentially fear the page is going to be permantently deleted.
After confirming the action, a snackbar notice will confirm the page has been 'moved to the trash'. Screenshot:
Once the page is in the trash, useres can permanently delete it. One of the available actions is 'Permanently delete'. Screenshot:
After clicking Permanently delete' there is no confirmation step. The page is permanently deleted right away. A snackbar notice will confirm the permanent deletion:
Overall, I think this flow is unclear and confusing for users.
Some history
Traditionally, the classic admin never implemented confirmation dialogs for the 'trash page' and 'delete permanently page' actions. The reasoning was that the first action isn't a destructive one. The second action is desctructive but users are in the context of hte 'trash' and it's clear enough that deelting from the trash deletes permanently.
Regardless od the historical approach illustrated above, it is worth considering whether it would be beneficial to think at a better flow. My 2 cents:
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: