Closed Bug 809757 Opened 12 years ago Closed 12 years ago

[Keyboard] No keyboard when trying to fill a field

Categories

(Firefox OS Graveyard :: Gaia, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:+)

VERIFIED FIXED
B2G C2 (20nov-10dec)
blocking-basecamp +

People

(Reporter: dscravaglieri, Assigned: rudyl)

References

Details

(Keywords: dogfood, smoketest, unagi)

Attachments

(2 files)

November 7 build
gecko-aurora: d782479f2838
gaia: a226cc9dea848eeeb87364b54fe7e472ae5a1366

The keyboard is very unstable, sometimes it doesn't appear when we need to fill a field.
blocking-basecamp: --- → +
Keywords: smoketest, unagi
Priority: -- → P1
Blocks: 809760
Assignee: nobody → schung
Severity: normal → critical
This may be a dupe of bug 808651
I see this issue during smoketesting today when trying to fill in the browser URL, but in other places such as contacts it seems to work.
ttaubert, are you seeing this also with your patch in bug 802073? If not then you might be able to fix this and other keyboard quirks altogether with that patch.
I could not reproduce this issue with,
 - The same Gaia rev.: a226cc9dea848eeeb87364b54fe7e472ae5a1366
 - unagi_stable_2012-11-07.zip
Marcia, David, thanks for the changeset version, can you provice some steps to reproduce in order to help developers figuring out what you did?

The usual format people use is:

----
Steps to reproduce:
 - Launch the ***** application
 - Click **** to go to ****
 - Click on field **** and wait for the keyboard
 - Type 'foo' in field ****
 - Click on field **** and wait for the keyboard

Expected result:
 - The keyboard shows up

Actual result:
 - No keyboard

-------
Here is my changeset info:

Gaia: 7ffd1c81db16bf0c6c3285a46259411d603109ca
Gecko: f059d3668a1acdeca0fac3c489205edcbe3c8779

Unfortunately I haven't been able to reproduce it consistently. To the best of my knowledge this was what I was doing when it happened (I was running the test of loading a site using wifi:

1. Launch the browser from the dock.
2. Wait for the home page to finish loading.
3. Select the URL field and try to type in a URL.

Expected:

The keyboard would appear

Actual:

No keyboard comes up.
Hi all, please also see Bug 809760
I think they are the same issue

---
## Repro :
1. Launch the contact app
2. Press "+" button to add a contact
3. Add a picture 
4. After return to add contact page, try to edit some fields (e.g. Name, Phone...)

## Expected:
* Keyboard will be triggered

## Actual:
* Keyboard didn't show up
David - it doesn't look like schung is available to look at this (no activity in this bug). Can you find another assignee that can investigate today?
Assignee: schung → dscravaglieri
Was just able to repro again during smoketesting:

## Repro :
1. Using a data connection, Launch the browser and navigate to cnn.com
2. Press "Bookmark" button and try to add the bookmark to your home screen
3. Navigate back to the URL bar and try to type something. 

## Expected:
* Keyboard will be triggered

## Actual:
* Keyboard doesn't show up
Milestoning for C2 (deadline of 12/10), as this meets the criteria of "remaining P1 bugs not already milestoned for C1".
Target Milestone: --- → B2G C2 (20nov-10dec)
This is preventing a stable update to our testers - David, can we get an assignee here?
Flags: needinfo?(dscravaglieri)
Assignee: dscravaglieri → rlu
Flags: needinfo?(dscravaglieri)
I could reproduce this issue only by John's repro steps in Comment 8.
--
If you launch an app. like contact or SMS without going into "add a picture", this issue would not occur.

Thanks.
It's almost as if the "add bookmark to homescreen" editing UI is open, but *behind* the browser. it doesn't show up when it should. it does show up if you hold down the home button and kill the browser via card view.
Probably same root cause as bug 791920
Probably the same issue as Bug 809760.

Fixed with:
https://github.com/mozilla-b2g/gaia/pull/6420 merged.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Defect is still reproducing using Unagi, build 20121231070201. Please see defect https://bugzilla.mozilla.org/show_bug.cgi?id=823645 for more info. 

## Repro Steps:
1. Launch Internet Browser from device
2. Navigate to www.gmail.com from URL link
3. Enter a valid username & password
4. Select "Compose" OR open existing email and tap "reply"
5. Select inside the text body area

## Actual Results: 
Virtual keyboard does not show up.

## Expected Results:
User must be presented with a virtual keyboard.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I wasn't able to reproduce following the steps in comment 17, but please file a separate bug for this issue.  The fix here covered the STRs from comment 13 and above; I can confirm that's fixed.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
this defect only reproduces when accessing Gmail through the browser, NOT Gmail app on Unagi. I just reproduced this on build 20130102070202
 verified on unagi build id:  20130103070201. Also, see. https://bugzilla.mozilla.org/show_bug.cgi?id=823645
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: