U1 login: user cannot type full username, the textfield gets rewritten

[Jonas G. Drange]

U1 authentication is difficult on Touch using the virtual keyboard, through a webapp wrapper.

Steps to reproduce:
1. Find the U1 launcher icon in the Application scope (you may need to expand the section by clicking the "Installed" header); start U1
2. At the top right of the page that opens, click the Login link
3. If not done by default, touch the username input box

Note: when the phone is in portrait mode, the keyboard starts in numerical mode, and the num/alpha toggle is unresponsive; switch to landscape and refocus the input box

[David Barth (dbarth)]

See quick video to get a general idea of the problem: http://www.youtube.com/watch?v=fpW7Q53OHTM

There are multiple issues:
- the textfield focus changes during the input sequence, resulting in input errors
- the textfield re-validates / re-wrtites its content during the input sequence, such that it is impossible to continue entering characters (not shown in the video)
- the textfield is seen as "numerical" by the virtual keyboard, which switches to numerical mode by default
- the textfield and surrounding HTML make it difficult to see the text while using the virtual keyboard

[Thomas Moenicke (thomas-moenicke)]

addressing the layout issue (numbers/characters), fix is here:
https://code.launchpad.net/~thomas-moenicke/ubuntu-keyboard/ubuntu-keyboard-keyboardcontainer/+merge/188568

[Thomas Moenicke (thomas-moenicke)]

the issue described above is fixed, for the issues in comment #1 we should open a new one if still valid

[David Barth (dbarth)]

Here is a new video that shows how the textfield is dynamically "edited": http://www.youtube.com/watch?v=RKz-o6rv8ic

Further to that I noticed 2 important things while experimenting with the login page:

1. I found errors in the webinspector console while doing this video (see @1:45) : they show that touch events did hit the javascript code of the login page, while they should probably have been seen only by the virtual keyboard itself; there is a sort of leak of events between the views

2. Worse: the above scenario occurs with a generic user-agent string that present us as a Webkit "Ubuntu Mobile" browser. However, If pretending to be a Mobile Safari browser, then the login page works almost perfectly. It seems that we're getting served the desktop version, and that this one updates the textfield and does input validation on the fly, creating all the problems with see with the virtual keyboard.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-keyboard - 0.99.trunk.phablet2+13.10.20131004-0ubuntu1

---------------
ubuntu-keyboard (0.99.trunk.phablet2+13.10.20131004-0ubuntu1) saucy; urgency=low

  [ Thomas Moenicke ]
  * KeyboardContainer more declarative to avoid timing issues, fixes
    part of #1233207 . (LP: #1233207)
  * shift state/key fixes . (LP: #1229114, #1231611)
  * using only one loader for character and symbol layouts .
  * fix popover.

  [ Guenter Schwann ]
  * Handle the case, that two keys are touched at the same time fixes
    LP: #1230003. (LP: #1230003)
  * fix popover.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 60
 -- Ubuntu daily release <email address hidden> Fri, 04 Oct 2013 02:44:45 +0000