-
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
Block API: try separate controls registration #60779
base: trunk
Are you sure you want to change the base?
Conversation
Size Change: +48 B (0%) Total Size: 1.75 MB
ℹ️ View Unchanged
|
I've been playing a bit with this in this pull request to understand better how it could help with disabling controls for connected block attributes and this looks promising 🙂 @ellatrix, I'd love to know more about the ideas you had in mind, what needs to be done to push this forward, and how I can help with it. If you don't have the bandwidth to work on it, I can try to take over it. A couple of comments so far:
|
@SantosGuillamot From my vantage point: Great job with the experiment so far! This is exciting.
On first thought, this makes sense to me (see caveat below though).
EDIT: If we want to pass the |
What?
This is just an idea to resolved the problem of disabling/omitting controls by attribute keys, for (but not limited to) block bindings. We could use this also for locking non content attributes, and it could also allow site admins to granularly control what block attribute controls can be used.
Why?
How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast