Closed Bug 1170611 Opened 10 years ago Closed 9 years ago

[Keyboard] Having a keyboard active will disable all app interaction if the user has typed anything

Categories

(Core :: Layout, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

VERIFIED FIXED
blocking-b2g 2.5+
Tracking Status
b2g-v2.2 --- unaffected
b2g-master --- verified

People

(Reporter: dharris, Unassigned)

References

()

Details

(Keywords: regression, smoketest, Whiteboard: [3.0-Daily-Testing])

Description: When the user types something into an app with the keyboard active, they will no longer be able to interact with any buttons within any app they are in. The Power button, Home button, Keyboard, and Edge Gestures will not be affected by this bug. Repro Steps: 1) Update a Flame to 20150602055237 2) Open an app with a keyboard, such as Messages 3) Tap on the new message Icon 4) Type a phone number into the "To:" Field 5) Select the Back button, "...", or "+" Actual: All app interaction will be disabled as long as the keyboard is active Expected: User is able to fully interact within any app with the keyboard open Environmental Variables: Device: Flame 3.0 (319mb)(Kitkat)(Full Flash) Build ID: 20150602055237 Gaia: 6d477a7884273886605049b20f60af5c1583a150 Gecko: 9eae3880b132 Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 Repro frequency: 3/6 50% See attached: Logcat, Video - https://youtu.be/ytOWnAj7JyA
This issue DOES occur on Flame 3.0 (512mb) All app interaction will be disabled as long as the keyboard is active Environmental Variables: Device: Flame 3.0 (512mb)(Kitkat)(Full Flash) Build ID: 20150602055237 Gaia: 6d477a7884273886605049b20f60af5c1583a150 Gecko: 9eae3880b132 Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 ========================================================================================================== This issue does NOT occur on Flame 2.2 User is able to fully interact within any app with the keyboard open Environmental Variables: Device: Flame 2.2 (319mb)(Kitkat)(Full Flash) Build ID: 20150602002504 Gaia: a675e5472944a9d7a16e091ba8a59901e37df9e0 Gecko: c163c2a5b921 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
[Blocking Requested - why for this release]: Functional regression that fails smoke tests. Requesting a window.
blocking-b2g: --- → 3.0?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
QA Contact: jthomas
QA Contact: jthomas
After further investigation with Jayme's help, it seems as though this bug has a 100% repro rate if the user is on 512mb memory, and they access the keyboard somehow before the device goes to sleep after a fresh flash, or reset. If the device does end up sleeing before accessing the keyboard this issue does not seem to appear.
QA Contact: jmercado
The changes for Bug 1153589 seem to have caused this issue. Mozilla-inbound Regression Window Last Working Environmental Variables: Device: Flame 3.0 BuildID: 20150601113741 Gaia: 85e6fcef45c0cb2c017739df42b68b96cf5bb9c3 Gecko: cc758e8f18e3 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 First Broken Environmental Variables: Device: Flame 3.0 BuildID: 20150601115340 Gaia: 85e6fcef45c0cb2c017739df42b68b96cf5bb9c3 Gecko: 4cb3a97de6ee Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 Last Working gaia / First Broken gecko - Issue DOES occur Gaia: 85e6fcef45c0cb2c017739df42b68b96cf5bb9c3 Gecko: 4cb3a97de6ee First Broken gaia / Last Working gecko - Issue does NOT occur Gaia: 85e6fcef45c0cb2c017739df42b68b96cf5bb9c3 Gecko: cc758e8f18e3 Gecko Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=cc758e8f18e3&tochange=4cb3a97de6ee
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Kartikaya, can you take a look at this please? This might have been caused by the landing for bug 1153589. This is a smoketest blocker so we may need the landing backed out.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(bugmail.mozilla)
Blocks: 1169735
Marking resolved fixed per backout in comment 6. Adding verifyme/qawanted to verify this is fixed in next available nightly with backout included.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
This issue is verified fixed on the latest 3.0 Nightly Flame build. Actual results: Having the keyboard active before the device sleeps does not prevent the user from interacting with the app. (5/5 tests) Environmental Variables: Device: Flame 3.0 BuildID: 20150603115939 Gaia: 477b5672811ed970a7476fe6f67dba546a302dce Gecko: 196d99aabc27 Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Depends on: 1172310
Blocks: 1174840
Moving the bug to the component where the regression came from.
Component: Gaia::Keyboard → Layout
Product: Firefox OS → Core
blocking-b2g: 2.5? → 2.5+
You need to log in before you can comment on or make changes to this bug.