Closed
Bug 1097943
Opened 10 years ago
Closed 10 years ago
[Window managment]When edge gesturing with Settings, Browser and marketplace, creates an unresponsive state
Categories
(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)
Tracking
(b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
DUPLICATE
of bug 1096704
People
(Reporter: rmitchell, Unassigned)
References
()
Details
(Whiteboard: [2.1-exploratory-3])
Attachments
(1 file)
90.50 KB,
text/plain
|
Details |
Description: With Software home button on and edge gesturing with Settings, Browser and marketplace, creates an unresponsive state Repro Steps: 1) Update a Flame to 20141112001201 2) Launch settings, browser and marketplace 3) Edge gesture from settings to browser and market place back and forth Actual: browser locks up, and flame becomes unresponsive Expected: No lock ups occur Environmental Variables: Device: Flame 2.1 (319mb)(Kitkat Base)(Shallow Flash) Build ID: 20141112001201 Gaia: 4c159e75a1568afbbf0c83c1235ec56facfbe87d Gecko: b9849b3c6aaa Version: 34.0 (2.1) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Repro frequency:75% See attached:logcat,video clip:https://www.youtube.com/watch?v=2jBMnts0PNA
Flags: needinfo?(dharris)
This issue DOES occur on 2.2 (319mb)(Kitkat Base)(Shallow Flash) Lockup occurs but with different visuals Flame 2.2 Device: Flame 2.2 Master (319mb)(Kitkat Base)(Shallow Flash) BuildID: 20141112040208 Gaia: 5ae28ff11b982e2bd7d1aa097cda131536952bdc Gecko: 688f821edcd4 Version: 36.0a1 (2.2 Master) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 ------------------------------------------------------------------------------------------------- Issue does not occur on 2.0 feature was not implemented yet Flame 2.0 Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash) BuildID: 20141112000204 Gaia: ab83632c92f9fc571b11d8468b6901cc4ed905c0 Gecko: 1ff99565be67 Version: 32.0 (2.0) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
[Blocking Requested - why for this release]: Nominating this to block on 2.1. This has a 75% repro rate which is fairly high, and the user will have to force close the browser and re open the window in order to get the page to load.
blocking-b2g: --- → 2.1?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
Whiteboard: [2.1-exploratory-3] [shb-enabled] → [2.1-exploratory-3]
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
blocking-b2g: 2.1? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•