-
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
Proposal: Add snackbar notification when unlocking content only blocks #61554
Labels
[Feature] Block Locking
The API allowing for the ability to lock/unlock blocks
[Type] Enhancement
A suggestion for improvement.
Comments
richtabor
added
[Type] Enhancement
A suggestion for improvement.
[Feature] Block Locking
The API allowing for the ability to lock/unlock blocks
labels
May 10, 2024
22 tasks
I don't think there's a way to add persistent snackbars for now, so that will have to be implemented separately. Do you think it's still worth it when the snackbar automatically dismisses itself after a timeout? |
Two things I've been thinking about in relation to this:
|
I opened #61845 to help testing and figure out a better UX. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
[Feature] Block Locking
The API allowing for the ability to lock/unlock blocks
[Type] Enhancement
A suggestion for improvement.
Perhaps there is a persistent snackbar that renders when you opt to unlock a content-only locked block.
This would allow you to easily re-lock a temporarily unlocked block, instead of having to find the "Done" control on the parent locked block. I'd expect that selecting "Done" in the block toolbar of the parent block would dismiss the snackbar, and clicking the "Lock" call the action would re-lock the block and dismiss the snackbar.
Perhaps the copy needs refinement, but I think it's an interesting approach to be able to easily re-lock a recently unlocked content-only block.
I thought of this while reviewing #61127.
The text was updated successfully, but these errors were encountered: