Closed
Bug 1069118
Opened 10 years ago
Closed 10 years ago
Video from youtube does not play in full screen when changed to landscape mode
Categories
(Core :: Audio/Video, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: poojas, Unassigned)
References
Details
(Whiteboard: [CR 723055][POVB])
Attachments
(1 file)
92 bytes,
text/plain
|
Details |
STR: 1. Open Browser app 2. open video in Youtube. 3. Screen should be in In portrait mode. 4. Select fullscreen 5. Change orientation to Landscape mode. 6. Change orientation back to Portrait then again landscape Expected result: Video playback should be continuous on orientation change Actual result: Video streaming stops/stuck in landscape mode. It starts again only when we change it back to portrait mode.
[Blocking Requested - why for this release]:
Comment 2•10 years ago
|
||
Ben, Dale, can you take a look here? Is this us or the media team?
Flags: needinfo?(dale)
Flags: needinfo?(bfrancis)
Comment 3•10 years ago
|
||
Can we see if this is a regression and do a branch check?
Keywords: qawanted
Comment 5•10 years ago
|
||
Cant reproduce on 2.1 either, I cant think of many ways we could effect this inside system, seems like it may be a media issue when it can be reproduced
Comment 6•10 years ago
|
||
I also can't reproduce this on 2.1 or master. I do see a slight flash of white on master when switching from landscape to portrait, but I can reproduce the bug described here, playback is continuous. Agree this would be difficult for us to change in the system app.
Flags: needinfo?(bfrancis)
Comment 8•10 years ago
|
||
If this wasn't working, then I'd expect it to be a core video/audio bug probably?
Component: Gaia::Browser → Video/Audio
Product: Firefox OS → Core
Also ni for Sushil if he suspects anything from HWC
Flags: needinfo?(sushilchauhan)
Updated•10 years ago
|
QA Contact: ddixon
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Updated•10 years ago
|
blocking-b2g: 2.1? → ---
Updated•10 years ago
|
Flags: needinfo?(hkoka)
You need to log in
before you can comment on or make changes to this bug.
Description
•