[GitHub issue by jds2501 on 2012-09-28T21:15:05Z, https://github.com/mozilla-b2g/gaia/issues/5455] ## Build * Device: Otoro * Gaia: dbe752c2bc61835a92469cb0e35ad5d938a754d5 * Mozilla Central: 5e9ba780a2f3db83364a87a7b976eafe4ae834b2 ## Steps 1. Select the identifier field for a wifi network 2. Lock the screen 3. Unlock the screen 4. Select the identifier text field again ## Expected The keyboard should come up. ## Actual Nothing happens. If you select a different text field (password for example), then select the identifier text field again, then the keyboard comes up.
[GitHub comment by jds2501 on 2012-09-28T21:17:34Z] This appears to also happen with the "title" field of a calendar add event page. I get the feeling this affects general use cases with text fields, the keyboard, and unlocking and locking the screen.
blocking+ since this is keyboard-less-ness all over the system then this happens (except in some places).
blocking-basecamp: ? → +
Summary: Typing the identifier for a wifi network, locking the screen, unlocking it, and selecting that field again does not pull up the keyboard → keyboard does not load in input fields after lock/unlock screen
This has been fixed by bug 796269.
Assignee: nobody → ttaubert
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Depends on: 796269
Resolution: --- → FIXED
Device: Unagi Build: 20130102070202 Does not repro
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.