← Back to team overview

ubuntu-webapps-bugs team mailing list archive

[Bug 1445171] Re: Oxide doesn't accept input on password fields if previous field had preedit

 

** Changed in: oxide
       Status: Confirmed => Fix Released

** Changed in: oxide-qt (Ubuntu)
       Status: Confirmed => Fix Released

** Changed in: oxide-qt (Ubuntu RTM)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1445171

Title:
  Oxide doesn't accept input on password fields if previous field had
  preedit

Status in Canonical System Image:
  Fix Released
Status in Oxide:
  Fix Released
Status in oxide-qt package in Ubuntu:
  Fix Released
Status in oxide-qt package in Ubuntu RTM:
  Fix Released

Bug description:
  Steps to reproduce

  1) Visit http://mobile.twitter.com in the browser

  2) Click login

  3) Enter the username "Hello"

  4) Tap the password field once, notice that it doesn't display the
  text cursor and the word ribbon is still displayed

  5) Type the password "hello123"

  Expected result

   The password "hello123" should be input.

  Actual result

   Only "123" is input, presumably because the keyboard is still sending
  data as pre-edit which oxide doesn't handle for passwords.

   After tapping the field a second time Oxide does disable pre-edit
  correctly.

   Additionally if backspace is pressed after entering "hello123" oxide
  will send incorrect surrounding text information to the keyboard
  triggering the crash logged here: https://bugs.launchpad.net/ubuntu-
  keyboard/+bug/1444947

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445171/+subscriptions


References