Closed
Bug 923855
Opened 12 years ago
Closed 12 years ago
[b2g] Pressing continue for pin entry requires pressing continue twice.
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
2013-10-14
People
(Reporter: muffinresearch, Assigned: muffinresearch)
Details
STR:
* Go to pin entry for a paid app
* Enter pin
* Press continue.
What happens:
* Note how when the keyboard dissappears the continue button is not pressed meaning you need to press continue a second time to submit your pin info.
What should happen:
You should be able to just click continue once.
| Assignee | ||
Updated•12 years ago
|
Summary: When entering your pin you lose focus on the trusted ui when the keyboard goes down. → [b2g] Pressing continue for pin entry requires pressing continue twice.
| Assignee | ||
Updated•12 years ago
|
Priority: -- → P3
Target Milestone: --- → 2013-10-07
| Assignee | ||
Comment 1•12 years ago
|
||
Comment 2•12 years ago
|
||
I see you have a fix so that's cool. Just curious, is this on device or desktop b2g or both?
| Assignee | ||
Comment 3•12 years ago
|
||
(In reply to Kumar McMillan [:kumar] from comment #2)
> I see you have a fix so that's cool. Just curious, is this on device or
> desktop b2g or both?
I've only seen this on device.
| Assignee | ||
Updated•12 years ago
|
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → All
| Assignee | ||
Comment 4•12 years ago
|
||
| Assignee | ||
Updated•12 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 5•12 years ago
|
||
This fix isn't working testing on -dev. Back to the drawing board!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Updated•12 years ago
|
Status: REOPENED → ASSIGNED
| Assignee | ||
Updated•12 years ago
|
Target Milestone: 2013-10-07 → 2013-10-14
| Assignee | ||
Comment 6•12 years ago
|
||
| Assignee | ||
Updated•12 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•