Closed Bug 862700 Opened 11 years ago Closed 10 years ago

[BROWSER] text area/text field doesn't trigger keyboard

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-)

RESOLVED WORKSFORME
blocking-b2g -

People

(Reporter: wachen, Unassigned)

References

Details

(Keywords: regression)

*Environment:
Phone - Unagi
pub pvt build v101(shira) 2013-04-16 eng build
build identifier 20130416230204

*How to reproduce:
1. Go to "browser"
2. Try to file a bug thru Bugzilla (login using persona)

*Expected Result:
  keyboard should be triggered when u tried to focus on description or summary column

*Actual Result:
  It didn't trigger the keyboard at all
this happen in v101(shira/tef) only. v110 is not reproducible.
blocking the re-verification of bug 811604
Blocks: 811604
blocking-b2g: --- → tef?
I can't reproduce this issue on inari for v1.0.1:
Gecko  http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/6bac24e14538
Gaia   c883af5ecd0998f78d9aaa4c2337c842e1dbb5a0
BuildID 20130416070200
Version 18.0
Inari
Tested on Inari, it was working fine.
It only didn't work on Unagi.
Unagis aren't shipping devices so we can't block on this.
blocking-b2g: tef? → -
Probably not worthwhile to get a regression window here if this is unagi-specific, as we probably aren't going to put a focus to fixing this anytime soon.
Component: Gaia::Browser → Gaia::Keyboard
The keyboard related work has changed a lot, including the inputmethod API.
So, close this bug we're not going to tackle this old bug on unagi.

Please help re-open it if you still can see this issue with current master.
Thanks.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.