Closed
Bug 1103843
Opened 11 years ago
Closed 11 years ago
[STK] Keyboard disappears during PIN enter
Categories
(Firefox OS Graveyard :: Gaia::System::Input Mgmt, defect)
Firefox OS Graveyard
Gaia::System::Input Mgmt
Tracking
(b2g-v2.1 unaffected, b2g-v2.2 affected)
RESOLVED
DUPLICATE
of bug 1100250
| Tracking | Status | |
|---|---|---|
| b2g-v2.1 | --- | unaffected |
| b2g-v2.2 | --- | affected |
People
(Reporter: mnjul, Unassigned)
References
Details
(Keywords: regression)
+++ This bug was initially created as a clone of Bug #1093471 +++
Per bug 1093471 comment 4:
> Created attachment 8527459 [details]
> 2014-11-24-07-05-54.png
>
> Behavior changed but is by any mean better :-(
> See attached screenshot.
> Now, when I focus PIN input, keyboard is no visible (white area) and no
> interacting any more, tapping to empty white space hides keyboard
> immediately, so I'm unable to enter PIN at all.
> When I press Home button (switch to home screen or another app) I see
> keyboard for first two seconds there (quite unexpectedly, it is the one
> which should be for STK PIN enter, for sure) and then it disappears.
> So for me it is some layering+race condition problem (IMHO)...
Screenshot is at https://bugzilla.mozilla.org/attachment.cgi?id=8527459 .
| Reporter | ||
Comment 1•11 years ago
|
||
Did a quick investigation and bug 1091483 seems to be the regression bug. We need to agree on a z-index such that Keyboard is top-more than icc-view -- :mancas, how do you think?
| Reporter | ||
Updated•11 years ago
|
Comment 2•11 years ago
|
||
Hi John, I've tried to reproduce the issue with the latest master but I can't do it. However I opened a follow up[1] of bug 1091483 which will fix an issue with the keyboard when trying to write in a STK message. I'm not sure about if that bug could solve this issue too.
I'll continue investigating it. Could you provide more info about the build and the commit?
Thanks!
[1] bug 1100250
Flags: needinfo?(b.mcb) → needinfo?(jlu)
| Reporter | ||
Comment 3•11 years ago
|
||
Hi :mancas,
I think bug 1100250 is actually the same issue as this bug. Your patch over there fix this bug too. Let me mark the duplication ;)
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(jlu)
Resolution: --- → DUPLICATE
Updated•11 years ago
|
blocking-b2g: 2.2? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•