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

Backspace and scroll makes text jerk when deleting many newlines #1

Open
karpelcevs opened this issue Jan 14, 2014 · 3 comments
Open

Comments

@karpelcevs
Copy link

First, thanks for fixing most of the iOS7 bugs! Unfortunately, there are still some more.

In the example project, add to the text quite a few simple newlines: \n\n\n\n\n\n\n\n\n\n\. It works also with letters and newlines, such as a\na\na\na\na\n etc.
Launch the app, tap the text.

First, ensure-visible issues:

  1. Text isn't scrolled to bottom, it stays somewhere in the middle.
  2. Second tap also doesn't scroll to bottom even though caret is now there.

Now, start tapping backspace. Newlines are removed, however:

  1. Big text piece from above is flashing at the top of the view right after pressing backspace and disappearing again (as if scrolling up and then down again).
  2. Caret is jumping somewhere up and then down again (I suppose this is the reason for jerking, but it's just a guess).

Important note, this is reproducible only when text is added prior to editing. Adding newlines from keyboard and then removing them does not reproduce the behaviour.

I'm trying to fix it in my app myself right now. If I'm successful, will add a pull request as well.

@getaaron
Copy link

@coverback Any luck solving this?

@karpelcevs
Copy link
Author

@getaaron no. Sad to say, I had to go live with this bug. Investigation showed that caret tends to be in incorrect position until at least a new event cycle completes, and I decided that a dirty hack by waiting could break more than solve.

steipete pushed a commit that referenced this issue Apr 29, 2014
Update from steipete:master
@poscar
Copy link

poscar commented May 2, 2014

Also experiencing this issue :(

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

No branches or pull requests

3 participants