-
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
Double enter should break out captions and lists (and similar) and onto a newline #579
Comments
I think number one seems expected. 3rd option: break out of the caption if the line is empty (so double enter to break out). This seems in line with WP's current block quote behaviour, where you break out the quote if you hit enter in the last paragraph and it is empty. Option 2 question: what happens if you're not at the end? |
I like that. Also handily provides an answer to your solid followup option 2 question. That being said, if we did go with option 2, pressing enter mid-sentence would, I suppose, split the stuff after the caret into a new paragraph. Which leads to option 4: don't do anything when you press enter. No new lines, no nothing. You'd have to use the arrow keys to exit the paragraph. |
+1 — this is how I'd expect it to work.
+1 to this as well :) |
I am not sure about breaking out of the caption with enter. |
Just to be clear, it's enter enter — that is, enter on an empty line. Would you prefer the way to break out of a caption would be tab or arrow keys? |
See also #374 |
The case where you start breaking within the middle of a caption complicates it. Also as we consider all the new blocks being created, "breaking" the content of a block field by hitting enter is going to be fragile and convoluted. I think in most cases we should just remain within the editable field you are in. |
Per this discussion, let's embrace the block, and close this for now. Tab will escape you. And if that isn't enough, we can reopen. |
From Ella:
This should apply captions and list blocks, and probably other similar ones.
The text was updated successfully, but these errors were encountered: