If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[Window Management] Picture and Video previews cannot be viewed landscape unless opened in a landscape-capable app



Firefox OS
Gaia::System::Window Mgmt
2 years ago
a year ago


(Reporter: Marty, Unassigned)



Gonk (Firefox OS)

Firefox Tracking Flags

(feature-b2g:3.0?, tracking-b2g:+, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)


(Whiteboard: [2.5-Daily-Testing][Spark][systemsfe], URL)


(1 attachment)



2 years ago
Created attachment 8637534 [details]

If the user opens a picture or video media file in a preview window (opening from mms, bluetooth transfer notification, download manager, etc.) they will not be able to rotate the display of the picture or video to landscape unless they were in a landscape app (browser, gallery) at the time they opened it.

This means that if they receive or download a widescreen video, and try to open it from a notification when at the homescreen, they will not be able to rotate the phone to view the video in landscape, and must watch the video shrunk down with a lot of wasted screen space.

Repro Steps:
1) Update a Aries to 20150722124026
2) Take a screenshot while at the homescreen
3) Tap the notification to open the image preview, then rotate the device to landscape orientation.

Media preview windows cannot go landscape unless opened while in a landscape-capable app

Media preview windows can be viewed landscape for picture and video files.

Environmental Variables:
Device: Aries 2.5
Build ID: 20150722124026
Gaia: b57aef5b7f52c40f88ee4c069ff722404e8e8521
Gecko: 954706e7611c
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 42.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Repro frequency: 10/10
See attached: logcat, Video (URL)

Comment 1

2 years ago
This issue DOES occur on Flame 2.5, 2.2, 2.1, and 2.0 builds
Media preview windows cannot go landscape unless opened while in a landscape-capable app

Environmental Variables:
Device: Flame 2.5
Build ID: 20150722010204
Gaia: 84c3bf622e211046d905803b34de5d331761f22d
Gecko: 8e5c888d0d89
Gonk: 41d3e221039d1c4486fc13ff26793a7a39226423
Version: 42.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Environmental Variables:
Device: Flame 2.2
Build ID: 20150721162504
Gaia: e1e6317f17a840b19af9dbb25f5a771d8d9fa161
Gecko: a73051740290
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Environmental Variables:
Device: Flame 2.1
Build ID: 20150721001206
Gaia: cc24cce17ab2ebf79f6505103da714fc65bc5ec1
Gecko: 3856aebece7b
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 34.0 (2.1)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Environmental Variables:
Device: Flame 2.0
Build ID: 20150721000210
Gaia: b16ba05481e577bc644ed8966f587a70fe2148e6
Gecko: 69dcc68fad52
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 32.0 (2.0)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
NI on component owner for nomination decision and assignment.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga) → needinfo?(ashiue)

Comment 3

2 years ago
[Blocking Requested - why for this release]:
This behavior is user unfriendly. Suggest to fix in the latest branch.

Hi Tim, could you please help to take a look at this issue? Thank you.
blocking-b2g: --- → 2.5?
Flags: needinfo?(ashiue) → needinfo?(timdream)
Whiteboard: [2.5-Daily-Testing][Spark] → [2.5-Daily-Testing][Spark][systemsfe]
Needs lots of work for little gain.
blocking-b2g: 2.5? → ---
Keywords: polish
I thought we implemented this. We should do this in future releases.
feature-b2g: --- → 3.0?
tracking-b2g: --- → +
Flags: needinfo?(timdream)
You need to log in before you can comment on or make changes to this bug.