Closed
Bug 1053348
Opened 10 years ago
Closed 10 years ago
[B2G][Loop] When rotating the phone to landscape, the video intro display upside down
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(b2g-v2.0 affected, b2g-v2.1 affected)
RESOLVED
WORKSFORME
People
(Reporter: psiphantong, Unassigned)
References
Details
(Whiteboard: [2.0-exploratory])
Attachments
(2 files)
Description: When rotating the phone 180 degrees and ending on landscape, the video intro before signing in display upside down Repro Steps: 1) Update a Flame (319mb) to 20140813000201 2) Go to the Loop App 3) Swipe through the intro text 4) On camera view, rotate the phone 180 degrees and end on landscape Actual: the video intro display upside down Expected: the video intro does not display upside down Environmental Variables: Device: Flame 2.0 (319mb) BuildID: 20140813000201 Gaia: cade2fdbb2230670788dcf2fc7b100f4a37b6458 Gecko: a7c673dae1ed Version: 32.0 (2.0) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Repro frequency: 3/3 See attached: screenshot and logcat attached
Reporter | ||
Comment 1•10 years ago
|
||
This issue also reproduce on Flame 2.1 (319mb), Buri 2.1, Flame 2.0 (512mb), Buri 2.0. The video intro display upside down. Flame 2.1 (319mb) Environmental Variables: Device: Flame Master Build ID: 20140813040202 Gaia: 9f35fca9d818b26c06aa6b7e5c0bef25886f8f20 Gecko: 7fc96293ada8 Version: 34.0a1 (Master) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Buri 2.1 Environmental Variables: Device: Buri Master Build ID: 20140813073008 Gaia: 9f35fca9d818b26c06aa6b7e5c0bef25886f8f20 Gecko: 76b55c0850ca Version: 34.0a1 (Master) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Flame 2.0 (512mb) Environmental Variables: Device: Flame 2.0 BuildID: 20140813000201 Gaia: cade2fdbb2230670788dcf2fc7b100f4a37b6458 Gecko: a7c673dae1ed Version: 32.0 (2.0) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Buri 2.0 Environmental Variables: Device: Buri 2.0 Build ID: 20140813063004 Gaia: e215fbf0cb16063b3d2f3e6a4e588c3550b6becb Gecko: 8e88a30eef43 Version: 32.0 (2.0) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 _________________________________________________________________________________________________________________________ This issue does not reproduce on the Flame 1.4 (319mb), Buri 1.4, and the Buri 1.3 because the feature was not supported. Flame 1.4 (319mb) Environmental Variables: Device: Flame 1.4 Build ID: 20140813063003 Gaia: 5bb0edb3446df787c48dbb37272827ad94cb9245 Gecko: 3d30ba3dc503 Version: 30.0 (1.4) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Buri 1.4 Environmental Variables: Device: Buri 1.4 Build ID: 20140813063003 Gaia: 5bb0edb3446df787c48dbb37272827ad94cb9245 Gecko: 3d30ba3dc503 Version: 30.0 (1.4) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Buri 1.3 Environmental Variables: Device: Buri 1.3 BuildID: 20140811024001 Gaia: 23f55be856cef53c6604a6fe4aeb09061afbc897 Gecko: ac685e277c7c Version: 28.0 (1.3) Firmware: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Reporter | ||
Comment 2•10 years ago
|
||
Comment 3•10 years ago
|
||
mbarone can you please take a look at this and weigh in on rather or not this is a blocker?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(mbarone976)
The dev team is working on landscape solutions, so probably it will be fix when the solution lands.
Flags: needinfo?(mbarone976)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Comment 5•10 years ago
|
||
This screen (the intro in the wizard) has been removed so it should not happen anymore.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•