Closed Bug 816915 Opened 12 years ago Closed 12 years ago

Keyboard doesn't disappear under certain condition

Categories

(Firefox OS Graveyard :: Gaia::Keyboard, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:+)

VERIFIED FIXED
B2G C3 (12dec-1jan)
blocking-basecamp +

People

(Reporter: alive, Assigned: ttaubert)

References

Details

Attachments

(1 file)

Attached file keyboard sticks to homescreen (deleted) —
This is another bug while working on bug 816008 I noticed. STR: 1. Open e-mail 2. Click new email 3. Click + to select contact 4. Click contact search input 5. Press home 6. Press home(This is not needed if bug 816878 is landed) Expected: keyboard disappears Actual: keyboard sticks to homescreen, and you even could click keys but you don't know where your input is going to... Note: IMO This is NOT dupe of 816052. Should be something wrong in window manager about blur (or gecko?). I bet this exists for a long time but after bug 808724 is landed, keyboard is brought to the very foreground so it's easier to reproduce.
I think this is a dupe.
Component: Gaia::System → Gaia::Keyboard
QA Contact: wachen
Whiteboard: DUPEME
This might be 812115
BB+, P2 - severe usability issue
blocking-basecamp: ? → +
Priority: -- → P2
Tim, this is another keyboard don't dissapear related bug. Let's see if you have an idea for it.
Assignee: nobody → ttaubert
Depends on: 816593
Joe - I noticed you flagged this as QA wanted but what specifically do you need us to do here? Thanks. :)
Flags: needinfo?(jcheng)
If this turns out to be a dupe of 811953, we can close it.
hi John, sorry for not putting on more comments. added qawanted to confirm if this is a dup of existing bugs. thanks
Flags: needinfo?(jcheng)
Alive, please provide more information on the build you are using. (commit code or date of release or blah blah blah Joe, the bug looks similar, but I don't think they are the same. I need more info on builds to validate the bugs
Flags: needinfo?(alive)
Keywords: qawanted
Whiteboard: DUPEME
Mass Modify: All un-milestoned, unresolved blocking-basecamp+ bugs are being moved into the C3 milestone. Note that the target milestone does not mean that these bugs can't be resolved prior to 12/10, rather C2 bugs should be prioritized ahead of C3 bugs.
Target Milestone: --- → B2G C3 (12dec-1jan)
I cannot reproduce with newest build :| Something is fixed.
Flags: needinfo?(alive)
I think this might have been fixed by bug 812115. Can someone please confirm and if not reproducible anymore resolve this?
Closing since #12
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: