-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Move positioning of page update success message #7276
Comments
This is another good reason for making that Post updated message auto-close, as it hides content - #4495 |
I would like us to consider not having this message at all. Could we update enough information in the 'saved' indicator without this? |
@karmatosed I'd say it's an option, however, there's a couple important considerations:
|
@pojke good points, I do think it's worth exploring though how this could look. Is it in the right place? Is it the right styling? |
It seems like this issue can be improved in two ways:
2 is somewhat bigger, but is probably the best long term fix for this. Things like "Post updated" and "Post published" are probably fine to fade out after a short delay, whereas things like "Post failed saving, connection issues" should not fade out. So let's keep this issue in the pool and hope that pull requests trickle in here! |
I added the
Regarding redesigning the UI for permalinks, I couldn't find an open issue for that. I organized open issues in to a label: https://github.com/WordPress/gutenberg/labels/Permalinks |
In WordPress 5.0 this behaviour is still there, with the updated notice blocking the permalink above the post/page title: Since WordPress < 5.0 supports notices with a |
I see a couple options here: 1. Title block becomes its own block. 2. Take advantage of the disabled "Publish" button. Current view: Possible iteration: I do believe the latter option fails in a couple ways:
|
Ultimately, if we think the Title Block issue will resolve this, we might be able to close this issue. Any thoughts? |
Glad to find this ticket again! It is a perfect ticket to keep open and resolve by porting the improvements that were made in #12301 (comment). I think I'll try and assign myself on this one and make that happen. To clarify — the improvements made in the PR linked above push down the editing canvas when notices appear. This solves the problem entirely, in a great way. Title block discussions are good to have, but IMO irrelevant to this ticket. |
When updating a permalink in Gutenberg and publishing the page, we're losing an access to the permalink. It's a bad UX as a user wants to confirm that the permalink is changed
Ideally the success message would be above the editor so there's no way it hovers over any element.
The text was updated successfully, but these errors were encountered: