Skip to content
This repository has been archived by the owner on Dec 12, 2018. It is now read-only.

Unable to place cursor close to beginning of line #192

Open
ruedigerkupper opened this issue Aug 28, 2018 · 5 comments
Open

Unable to place cursor close to beginning of line #192

ruedigerkupper opened this issue Aug 28, 2018 · 5 comments

Comments

@ruedigerkupper
Copy link

Device: hammerhead
Version: OTA-4

While typing a message I am unable to place the cursor at the first 3 to 4 characters in any line. I have no problem at all placing it at a later point, but not close to the start.

This does not occur in other apps (like in the browser app I am typing right now). And it is no hardware issue with my device, since it also appears in landscape mode where the left edge of the entry field is located at the middle of the screen. It must be a software issue.

@advocatux
Copy link
Contributor

You can't place the cursor tapping but you can place it using the keyboard in joystick mode or whatever is that mode called (press&hold space bar, the keyboard goes blank, move the cursor like a joystick)

@ruedigerkupper
Copy link
Author

That's right and that's how I do it currently. But it is certainly not by intention that you can't place the cursor here?

@ruedigerkupper
Copy link
Author

@advocatux
But that means you confirm this bug? On which device and build?

@advocatux
Copy link
Contributor

Hmm interesting, today I can place the cursor tapping at the beginning of the line both in krillin & hammerhead, both running xenial devel up to date, but yesterday I couldn't do it.

The intriguing part is that hammerhead has been updated today but krillin has not.

Anyway the tapping to put the cursor at the beginning works pretty unreliable and erratic. Afaik it has been always that way, even in vivid.

More than a bug this is a little annoyance to me.

@ruedigerkupper
Copy link
Author

Yes, it probably was there from the beginning. I never paid much attention, but the more often you type messages, the more annoying it gets.
Does anyone have an idea what causes this problem? This is probably some standard editable field (sorry, I'm not so much in mobile programming). It strikes me as very strange that it has problems with cursor positioning? If so, this will probably occur elsewhere?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants