-
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
Separator, Code: don't require Enter for shortcut #63654
base: trunk
Are you sure you want to change the base?
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @jarekmorawski. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: +168 B (+0.01%) Total Size: 1.75 MB
ℹ️ View Unchanged
|
It's testing well for me in both editors. Nice work! 🙌 Site editorsite-editor.movPost editorpost-editor.mov |
What?
Introduces a new transform/shortcut type
input
, which transform text into a block as soon as the sequence is complete (instead of waiting forEnter
).Question: in case of the separator, would it make more sense to also add an empty paragraph after it?
Why?
Because currently the
enter
shortcut is not discoverable enough, and there's not really any harm in transforming sooner. It's still possible to undo the transform.How?
Testing Instructions
Testing Instructions for Keyboard
Type
---
or```
in a paragraph block, which should transform it to a Separator or Code block respectively.Screenshots or screencast