Closed Bug 894259 Opened 11 years ago Closed 9 years ago

[Buri][Settings]DUT often can't invoke the number keyboard in PIN entering interface.

Categories

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

Product:
Firefox OS Graveyard
Component:
Gaia::Settings
Type:
defect

Tracking

(blocking-b2g:-)

Status:
RESOLVED WORKSFORME
Project Flags:
blocking-b2g -

People

(Reporter: sync-1, Assigned: alive)

References

Details

(Whiteboard: [WINDOW_MANAGER])

Attachments

(2 files)

The log
592.06 KB, text/plain
Details
2013-07-31-20-19-46.png
150.85 KB, image/png
Details
AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.152 Firefox os v1.1 Mozilla build ID:20130702230206 Created an attachment (id=462615) The log DEFECT DESCRIPTION: DUT often can't invoke the number keyboard in PIN code entering interface . REPRODUCING PROCEDURES: 1.Access Setings app.->SIM Security->Enable SIM PIN->Disable SIM PIN->Input wrong old PIN for three times->Done->Click Home key twice->On Enter PUK code screen->After enter PUK code,move cursor to "Create PIN"->or "Confirm new PIN"->You won't see number keyboard,so can't be done successfully-> KO 2.Restart DUT->After enter PUK code,move cursor to "Create PIN"->The number keyboard will appear. DUT = device under test EXPECTED BEHAVIOUR: DUT should invoke the number keyboard in PIN code entering interface normally.->OK ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: Mid REPRODUCING RATE: 5/5 For FT PR, Please list reference mobile's behavior:
Clone from brother
Attached file The log —
Dear Fabien, Can you find someone to check this?
Flags: needinfo?(kaze)
Dear Daniel, Can you find someone to check this? Thank you.
Flags: needinfo?(kaze) → needinfo?(dcoloma)
blocking-b2g: --- → leo?
After check, we found that is caused by some logic deal in /gaia/apps/system/window_manager.js. Is there anyone can check this?? Thanks a lot!
Dear Alive, Could you check on this? Thank you!
Flags: needinfo?(dcoloma) → needinfo?(alive)
Partner triage - consider non-blocker given the steps required to hit this bug. Please renom if this bug appears easier than is described in comment 0.
blocking-b2g: leo? → ---
Dear all: This issue also happened in Browser, modify PIN number in Settings,Everything.me and other Apps. Thanks!
blocking-b2g: --- → leo?
just like the bug #896359. It's a comment issue of gaia.
steps-wanted for comment 8. Can we try a number <input> in the Browser to verify this issue is occurring for others? If this is an issue that's quickly reproducible, we may block.
Keywords: steps-wanted
Dear Alex, Here is the steps to reproduce in browser: 1.launch browser 2.press home button of the phone twice or more 3.tap in the address label and the keyboard didn't display. ps: AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.158 Firefox os v1.1 Mozilla build ID:20130709070206
Flags: needinfo?(akeybl)
AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.164 Firefox os v1.1 Mozilla build ID:20130715070218 Still not OK. And I think it's an seriouse problem. Is there anybody can decide on this?
(In reply to xiaokang.chen from comment #11) > Dear Alex, > Here is the steps to reproduce in browser: > 1.launch browser > 2.press home button of the phone twice or more > 3.tap in the address label and the keyboard didn't display. > > ps: > AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.158 > Firefox os v1.1 > Mozilla build ID:20130709070206 I don't understand those steps, after clicking the home button (2) the browser disappears so I cannot tap in the address label. Could you please be more specific?
Flags: needinfo?(chenxk)
Dear Daniel, Sorry for my fault. The STR : Here is the steps to reproduce in browser: > 1.launch browser > 2.press home button of the phone twice or more > 3.tap the browser icon to enter the browser again > 4.tap in the address label and the keyboard didn't display.
Flags: needinfo?(chenxk)
Flags: needinfo?(akeybl)
OK I reproduced and this seems not a regression..
Assignee: nobody → alive
Flags: needinfo?(alive)
Confirmed. Root cause: when the user clicks the home button quickly, WindowManager does send appwillopen event but the following appopen event isn't fired. So KeyboardManager would think now app is still closing even the app is closed or opened.
Whiteboard: [WINDOW_MANAGER]
Keywords: steps-wanted
Removing steps-wanted per STR confirmation in comment 14 with testing done on comment 15 & comment 16.
Dear Alive, Any update obout this? Thanks!
George or Alive, can either of you confirm the dupe either from code or by testing with the patch available in bug 869393? Once confirmed we can close this off. Xiaokang, feel free to test out the patch in bug 896393 also to see if this resolves your problem here.
Flags: needinfo?(gduan)
Dear Wayne, in our side, the gaia commit info is :a381f29210dc11d312a9211f9148a19534a7278c 1374810734 and the patch of bug 869393 didn't match in our side.
Stay tuned please, the patch of bug 896393 is not r+ed.
Blocking as a dependent of bug 896393 to see if that helps but this might be a more generic version of the issue in that bug and worth investigating.
blocking-b2g: leo? → leo+
Depends on: 896393
I believe patch of 896393 would resolve this.
Flags: needinfo?(gduan) → needinfo?(chenxk)
Attached image 2013-07-31-20-19-46.png —
Dear Alive, 896393's patch fixed the problem, but has a regression like the picture of attachment. The STR : 1 add the patch of 896393 2 enter three times wrong sim pin so we see the page require puk code 3 enter the puk, new pin, confirm pin then press home button (note: don't press the ok button) 4 then will see the picture in the attachment I don't know why it occurs and didn't find the problem in other senarios up to now. Can you check it ? By the way, do you think the patch of 896393 can solve the problem of #898944 ??
Flags: needinfo?(chenxk)
(In reply to xiaokang.chen from comment #25) > Created attachment 784155 [details] > 2013-07-31-20-19-46.png > > Dear Alive, > 896393's patch fixed the problem, but has a regression like the picture of > attachment. > The STR : > 1 add the patch of 896393 > 2 enter three times wrong sim pin so we see the page require puk code > 3 enter the puk, new pin, confirm pin then press home button (note: don't > press the ok button) > 4 then will see the picture in the attachment > > I don't know why it occurs and didn't find the problem in other senarios up > to now. Can you check it ? File a new bug for regression. > > By the way, do you think the patch of 896393 can solve the problem of > #898944 ?? Nope I think.
Could you test again without patch of bug 896393? I tested it and the bug from comment 25 remains. I still open a bug 900355 for that.
Flags: needinfo?(chenxk)
chenxk@tcl.com, Please re-nom based on tests.
blocking-b2g: leo+ → leo?
(In reply to George Duan [:gduan] from comment #27) > Could you test again without patch of bug 896393? > I tested it and the bug from comment 25 remains. I still open a bug 900355 > for that. yes, you are right. Thanks a lot!
Flags: needinfo?(chenxk)
leo- this bug. As we understand it, this bug (894259) will also be fixed with the patch for bug 900355
blocking-b2g: leo? → -
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: