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

Bug #1445171 reported by Michael Sheldon
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
Critical
Unassigned
Oxide
Fix Released
Critical
Michael Sheldon
oxide-qt (Ubuntu)
Fix Released
Undecided
Unassigned
oxide-qt (Ubuntu RTM)
Fix Released
Undecided
Unassigned

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

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

may need to send a hotfix for this

Changed in canonical-devices-system-image:
importance: Undecided → Critical
status: New → Confirmed
tags: added: hotfix
Changed in canonical-devices-system-image:
milestone: none → ww17-2015
Olivier Tilloy (osomon)
Changed in oxide:
status: New → Confirmed
Changed in oxide:
importance: Undecided → Critical
assignee: nobody → Michael Sheldon (michael-sheldon)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in oxide-qt (Ubuntu):
status: New → Confirmed
Revision history for this message
Michael Sheldon (michael-sheldon) wrote :

This appears to be a Chromium bug, which has the final result of the wrong field type being set; however it's fixed with Chromium 43 (which oxide 1.7 is based on). So my recommendation would be that we provide the fix for the keyboard crashing in the hotfix release without any change to oxide, as this mitigates the biggest element of the problem (that the keyboard crashes) and the issues in oxide will then be resolved as soon as oxide 1.7 is released.

Revision history for this message
David Barth (dbarth) wrote : Re: [Bug 1445171] Re: Oxide doesn't accept input on password fields if previous field had preedit

+1 oxide-1.7 is really around the corner

On Wed, Apr 22, 2015 at 2:02 PM, Michael Sheldon <
<email address hidden>> wrote:

> This appears to be a Chromium bug, which has the final result of the
> wrong field type being set; however it's fixed with Chromium 43 (which
> oxide 1.7 is based on). So my recommendation would be that we provide
> the fix for the keyboard crashing in the hotfix release without any
> change to oxide, as this mitigates the biggest element of the problem
> (that the keyboard crashes) and the issues in oxide will then be
> resolved as soon as oxide 1.7 is released.
>
> --
> You received this bug notification because you are a member of Oxide
> Developers, which is subscribed to oxide-qt in Ubuntu.
> Matching subscriptions: oxide in Ubuntu
> https://bugs.launchpad.net/bugs/1445171
>
> Title:
> Oxide doesn't accept input on password fields if previous field had
> preedit
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445171/+subscriptions
>

Changed in canonical-devices-system-image:
milestone: ww17-2015 → ww19-ota
tags: removed: hotfix
Changed in canonical-devices-system-image:
milestone: ww19-ota → ww21-2015
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Oxide 1.7.8 is in ota4

Changed in canonical-devices-system-image:
milestone: ww21-2015 → ww22-2015
status: Confirmed → Fix Released
Olivier Tilloy (osomon)
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.