-
Notifications
You must be signed in to change notification settings - Fork 58
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
Keyboard automatically resigns and becomes active in an infinite loop #6002
Comments
I managed to stop it be pressing (+) a few times. |
I was able to reproduce it again without doing anything special. I was just adding more blocks. Here are some more videos to demonstrate what's happening. I'm not performing any interactions. I managed to close it https://github.com/wordpress-mobile/gutenberg-mobile/assets/1567433/f28edeae-5aeb-4725-afc4-372e0b25711b |
Thanks @kean for reporting this! It would be worth us testing on or after |
Hey @kean 👋 we are currently working on a fix for this, would you mind testing this build when you have a chance to see if it fixes it for you? Any feedback would be appreciated, thank you! |
Hey @geriux, thanks for addressing it so quickly. I tested it, and after adding hundreds of blocks, it's still going strong with no issues. It feels snappier too; maybe it's just me. Unrelated:
|
Thank you for testing! Happy to see that it fixed the issue for you! And that it feels snappier 🎉
Those are great suggestions! Hopefully, we'll be able to avoid hiding/showing the Keyboard in the future when we improve the current implementation we have with Aztec. As for the placeholder, I'll create an issue to track it. Thanks again! |
Describe the bug
Keyboard automatically resigns and becomes active in an infinite loop without any user interactions.
To Reproduce
Steps to reproduce the behavior:
Can't provide these. I've been simply adding one block type after another to monitor the memory usage. At some point, I saw two "Start typing..." blocks at the bottom and the keyboard started doing it.
Expected behavior
n/a
Screenshots
RPReplay_Final1690480652.mp4
Smartphone (please complete the following information):
trunk
from the commit wordpress-mobile/WordPress-iOS@8f1a857Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: