Closed Bug 990847 Opened 12 years ago Closed 8 years ago

[Sora][Settings]MS popup white screen when set phone lock.

Categories

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

defect

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: sync-1, Unassigned)

Details

(Keywords: regression, Whiteboard: [DUPEME])

Attachments

(1 file)

DEFECT DESCRIPTION:MS popup white screen when set phone lock. REPRODUCING PROCEDURES: Enter into Settings->Screen lock->Lock screen->Passcode lock->popup once white screen.--->KO Beetle_Lite_FF is OK. EXPECTED BEHAVIOUR: No popup anything. reproducing rate:100% ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE:5/5 For FT PR, Please list reference mobile's behavior:
Attached video ko-vedio —
It's blocker to carrier.
blocking-b2g: --- → 1.3?
Adding qawanted to see if we can confirm this on Moz side on 1.3.
Keywords: qawanted, regression
If click the screen when the screen is white, it will become screen withe unless reopen setting.
Jack this is really a very minor issue, and not something we should be blocking on given where we are in 1.3.
blocking-b2g: 1.3? → backlog
Whiteboard: [DUPEME]
Keywords: qawanted
(In reply to bhavana bajaj [:bajaj] from comment #5) > Jack this is really a very minor issue, and not something we should be > blocking on given where we are in 1.3. This bug reported during carrier IOT, and it will cause serious freezing issue when click on screen before virtual keyboard slide out. User need to kill setting app or press the back button which concealed by white screen. Therefore, I think it's blocker.
blocking-b2g: backlog → 1.3?
(In reply to Jack Liu from comment #6) > (In reply to bhavana bajaj [:bajaj] from comment #5) > > Jack this is really a very minor issue, and not something we should be > > blocking on given where we are in 1.3. > > This bug reported during carrier IOT, and it will cause serious freezing > issue when click on screen before virtual keyboard slide out. > > User need to kill setting app or press the back button which concealed by > white screen. > > Therefore, I think it's blocker. It looks like the white screen appears for less than a second, so unless you really are trying to get the screen frozen by stress testing it, I am not sure this is a valid usecase and a show-stopper for the device to ship. Also keep in mind the fact that this issue happens only when you set your passcode (which is not something a user would do on daily basis). Keeping those in mind can we get a waiver here for this cycle and something we will address in 1.4 ?
Discussed offline - this is too minor to block 1.3 at this time, so moving to 1.4? for triage.
blocking-b2g: 1.3? → 1.4?
I think this is too minor to block on any release. There is probably some viewport issues here -- we do CSS transitions on panels to create the transition animation, but at the same time the viewport moves when we attempt to focus keyboard input to an input field on the panel.
Vance - We're not going to block on this - it's too minor. Can you communicate with TCL about this?
Flags: needinfo?(vchen)
blocking-b2g: 1.4? → backlog
Flags: needinfo?(vchen)
blocking-b2g: backlog → ---
link all Fire C (codename: Sora) bugs to a meta one.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: