Skip to content
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

FIX empty block creation on device running AOSP keyboard #857

Merged

Conversation

daniloercoli
Copy link
Contributor

This PR fixes #856 by making sure to check if text listeners are enabled before doing any text/block manipulating action onEnter or onBackSpace.

In this particular case the BackSpace.Key detection code in Aztec is called when the initial empty HTML content is set to the block via setTextFromJS. Text listeners are disabled in this case, and those are not running, but InputFilters are not disabled.... By the way, I guess a better fix would involve changes to Aztec, but probably is easier to fix them here, since this change could also fix other potential problems in the future.

Steps to repro:

  • Start the demo app on STOCK emulator (Check AOSP keyboard)
  • Insert a new empty para block
  • Make sure it stays on the screen

@daniloercoli daniloercoli added the [Type] Bug Something isn't working label Apr 11, 2019
@daniloercoli daniloercoli added this to the v1.3 milestone Apr 11, 2019
@mkevins
Copy link
Contributor

mkevins commented Apr 11, 2019

I just tested this on Android emulator, and it works. It also fixes this: #783 . 🎉

@daniloercoli daniloercoli merged commit e2a454c into develop Apr 11, 2019
@daniloercoli daniloercoli deleted the issue/856-empty-block-creation-fails-on-AOSP-keyboard branch April 11, 2019 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Android - Problem with the AOSP keyboard and new block creation
2 participants