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

Issue/464 missing suggestions #466

Merged
merged 40 commits into from
Nov 16, 2017
Merged

Issue/464 missing suggestions #466

merged 40 commits into from
Nov 16, 2017

Conversation

0nko
Copy link
Contributor

@0nko 0nko commented Aug 14, 2017

Fixes #464. This brings back #237.

@0nko 0nko requested a review from khaykov August 14, 2017 11:27
@khaykov
Copy link
Member

khaykov commented Aug 15, 2017

There is another, a bit more serious side effect of #237 - when you delete the last character of styled text the span is removed from it. Open the app with demo content, put cursor behind "Italic" and press backspace on the software keyboard.

I researched this problem a long time ago, and it is indeed caused by autocorrect/suggestion (the suggested text becomes Underlined and all the other spans are removed from it). That's why we reapplying the spans here. But apparently it did not work :) I'll take a look at #237 - maybe it will be a quick fix.

@khaykov
Copy link
Member

khaykov commented Aug 15, 2017

Another issue - type some letters, toggle inline style, type some more letters, press space. Notice the inline style disappeared.

@0nko
Copy link
Contributor Author

0nko commented Aug 15, 2017

Hmm, that's pretty serious. Thanks for pointing that out, Klym.

@maxme
Copy link
Contributor

maxme commented Oct 19, 2017

@khaykov I can't reproduce issues you described. Is this specific to a certain android version or device? I tested on this branch, I used Android 5.0 and 7.0.

@khaykov
Copy link
Member

khaykov commented Oct 19, 2017

@maxme Yes, those issues are from pre 5.0.0 devices.

From the top of my head here is a couple of issues you can reproduce on 5.0.0+ devices (tested on Pixel_API_25 emulator):

Load empty editor, type "h" toggle bold, type "ello" notice that after you finish typing only the last letter will have a bold style applied to it.

Toggle bold, and type some incorrect word, like "herro", press space so it will be autocorrected to "hero", press backspace to cancel autocorrect and notice that the bold style is also gone.

Also, autocorrect only works with soft keyboard, so make sure to use it.

@khaykov
Copy link
Member

khaykov commented Oct 20, 2017

Found another issue that I can only reproduce on API 26 so far:
Load empty editor, type "a" toggle Bold style, type "b". Put the cursor between "a" and "b" and press space. Notice that "b" became unstyled.

:(

khaykov and others added 14 commits October 23, 2017 00:31
…mobile/WordPress-Aztec-Android into issue/fixing-spellcheck-removing-styling

# Conflicts:
#	aztec/src/main/kotlin/org/wordpress/aztec/AztecText.kt
#	aztec/src/main/kotlin/org/wordpress/aztec/formatting/InlineFormatter.kt
…mobile/WordPress-Aztec-Android into issue/fixing-spellcheck-removing-styling

# Conflicts:
#	build.gradle
…-removing-styling

Issue/fixing spellcheck removing styling
@mzorz mzorz self-assigned this Nov 13, 2017
@mzorz
Copy link
Contributor

mzorz commented Nov 14, 2017

  • tests run alright for me
  • Tested behaviour described in Can't remove styling when writing text #237 on Google Pixel, Android 8, works fine.
  • Tested on Nexus 6P, API 25, works fine
  • Tested on a geny image of Samsung Galaxy S3, Android 4.2.2, the behavior described in Can't remove styling when writing text #237 is not observed here, but a curious problem appears, that I did not observe on the base branch (develop): there are no newlines ,it seems everything is on the same line, and tapping return on the soft keyboard doesn't have any effects. See the gif below showing that I navigate the contents by moving the cursor to the right only:

aztec_horizontal

@mzorz
Copy link
Contributor

mzorz commented Nov 15, 2017

Just for the record: this comment #466 (comment) in this PR doesn't block the review/merge.

@mzorz
Copy link
Contributor

mzorz commented Nov 16, 2017

@0nko I confirm I can reproduce this issue here #466 (comment)

We can merge this one once the conflicts are resolved, going to open new issues with whatever is found (that comment for example, plus the all-content-in-one-line issue from 4.2.2 )

@mzorz
Copy link
Contributor

mzorz commented Nov 16, 2017

:shipit:

@mzorz mzorz merged commit e16bf94 into develop Nov 16, 2017
@0nko 0nko deleted the issue/464-missing-suggestions branch February 19, 2019 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants