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

[Android] List Block's caret positioning is off when new item at the end #845

Closed
hypest opened this issue Apr 9, 2019 · 1 comment · Fixed by #868
Closed

[Android] List Block's caret positioning is off when new item at the end #845

hypest opened this issue Apr 9, 2019 · 1 comment · Fixed by #868
Labels
[OS] Android [Type] Bug Something isn't working
Milestone

Comments

@hypest
Copy link
Contributor

hypest commented Apr 9, 2019

When there are a few empty list items, trying to add a new item at the end will not place the caret correctly.

  1. Do a long list, long enough to have a few empty list items here and there
  2. Try to add a new item at the end of the list
  3. Notice that the caret doesn't land on the new list item but rather, goes "back". The more empty lines from 2., the more chars the caret goes back.
@hypest hypest added [Type] Bug Something isn't working [OS] Android labels Apr 9, 2019
@hypest hypest added this to the v1.3 milestone Apr 9, 2019
@hypest hypest mentioned this issue Apr 9, 2019
5 tasks
@hypest
Copy link
Contributor Author

hypest commented Apr 12, 2019

Leaving some context from my investigation so far:

Our current method of setting the selection/caret via JS is not compatible with the way Aztec computes its char positions, especially with content like lists where there are special character in place to implement the list behavior. Those special characters (zero-width-spaces) take up char positions and the JS side doesn't know that. Will need to find a way to reconcile those two models.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[OS] Android [Type] Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant