-
Notifications
You must be signed in to change notification settings - Fork 4.7k
[Mobile] - Autocomplete - Fix regression related to the Enter key code #45997
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
Conversation
…erter where the enter key would fail to create the block and instead it creates a new Paragraph block
|
|
|
Size Change: 0 B Total Size: 1.32 MB ℹ️ View Unchanged
|
|
E2E tests related to the slash inserter passed correctly in wordpress-mobile/gutenberg-mobile#5280 |
SiobhyB
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works perfectly for me, thanks @geriux! ![]()
I noticed that there's a persistent failing test, but it doesn't appear related to any of the code in this PR. I'm guessing an updating from trunk will fix things up.
Related PRs:
Gutenberg Mobile-> [Mobile] - Autocomplete - Fix regression related to the Enter key code wordpress-mobile/gutenberg-mobile#5280What?
This PR fixes a regression introduced by #45510 where it changed getting the keyboard code from the
keyattribute which is being deprecated in the Web standards tocode.This is related to a previous effort (see #43521) to update the mobile code to this new attribute.
Why?
To fix the functionality of the autocomplete also known as slash inserter.
How?
Now it will add the
codeattribute through thecustomEditableOnKeyDowncallback event.Testing Instructions
/imageand tap on the return key of the keyboardScreenshots or screencast