Closed Bug 1104105 Opened 10 years ago Closed 10 years ago

[FFAndroid] PIN text box cannot be focused after a wrong PIN is entered

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P3)

x86_64
Android
defect

Tracking

(Not tracked)

VERIFIED FIXED
2014-12-22

People

(Reporter: julian.mozbugs, Assigned: muffinresearch)

References

Details

Attachments

(1 file)

Steps to reproduce: 1. Load MP-stage homepage logged in on your Android device. 2. Search for a paid app. 3. Press the Price button to initiate a purchase. 4. Enter a wrong PIN and press the Enter button. 5. Focus the PIN text box to re-enter the PIN. Expected results: The numeric keyboard is displayed and the user is able to re-enter the PIN. Actual results: The PIN text box cannot be focused and the PIN cannot be re-entered. Notes/Issues: Verified on FF33 (Android 4.2.1).
I can repro this. I've checked - it doesn't appear to be anything new. The cause looks to be the window.focus that we do as a workaround for focus issues in the trusted UI. We need to conditionally not do that for Android and that should fix it.
Assignee: nobody → scolville
Summary: PIN text box cannot be focused after a wrong PIN is entered → [FFAndroid] PIN text box cannot be focused after a wrong PIN is entered
Priority: -- → P3
Target Milestone: 2014-11-25 → 2014-12-02
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
I can still reproduce this issue in https://marketplace.allizom.org/ on FF 34 (Android 4.2.1)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: 2014-12-02 → 2014-12-16
(In reply to Iulian Timis from comment #4) > I can still reproduce this issue in https://marketplace.allizom.org/ on FF > 34 (Android 4.2.1) This wasn't on stage yet. I've updated the milestone to reflect what it should be.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Hmm re-testing this it's intemittently still happening on FFAndroid 34 / on an s3.
Talking to JulianT and running through this bug we discovered this un-desirable state still occurs only when using the enter key on the android keyboard but not when using the submit button. Going to double check there's nothing odd in the submit code and then file a platform bug once I've confirmed it's not our code.
Ah found that the code that attempts to disable the button is causing the behaviour on FFAndroid. New PR which should fix it is here: https://github.com/mozilla/spartacus/pull/179
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Target Milestone: 2014-12-16 → 2014-12-23
Verified as fixed in https://marketplace.allizom.org/ on FF 34 (Android 4.2.1). Attaching postfix screenshot. Closing bug.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: