-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[UX] Better content deletion confirm forms. #3162
Comments
@klonos In the sandbox site I saw that the sentence |
Changes:
|
@olafgrabienski, yeah, sorry, I had typed my previous comment in the morning, after filing the PR, but forgot to press "save" 😄 ...as I explain above, I added that text there because the page seemed too "blank" when deleting an individual piece of content (via the operations drop-button). When deleting via the bulk operations (even if a single pice of content has been selected), that space is filled with a list of pieces of content to be deleted, so that is not "a problem" in that case. I wanted to get some feedback before adding the same text in the bulk operations confirmation page too. I am trying to make our UI more smart/intuitive, and to be suggesting things for newcomers where it makes sense. If this feels like out of scope, I can revert that change (and stop doing that in general). If people think that this makes a better product, then I can be adding these small snippets here and there as I am fixing things in the UI. All feedback appreciated. |
In https://user-images.githubusercontent.com/2423362/40892440-87627038-67da-11e8-8be9-fc88e1290881.png, why is there a left padding before the "If you need..." sentence ? |
@opi I have not touched the style of that at all. This must be the default padding that comes with the description. Don't have the time to look into it now, but promise to do so soon. |
An improvement. However, I'm not sure we can assume a "visitor" can't see unpublished content. It depends on permissions and whether they are logged in or not. |
Valid point @herbdool 👍 ...adding a check on permissions so to conditionally show the message seems overkill for a help text (not that we are not doing that elsewhere), so I could just remove the text. Waiting for some more feedback before I update the PR. |
I'm worried about using messages directly in the form definitions like this. I've seen this problem previously where the message can end up being displayed after the form is submitted. It also makes it so that the form can't be embedded anywhere else, because the message will be shown at the top of the entire page. Aesthetically I think this is an improvement. I'm not sure if my technical complaint is sufficient argument against a UX improvement. |
I think we can get around the issue of having the warnings "bleed" into other pages either by using a blank |
Perhaps #3329 can help here as well. |
Before:
After:
PR by @klonos: backdrop/backdrop#2221
The text was updated successfully, but these errors were encountered: