Closed
Bug 776927
Opened 12 years ago
Closed 12 years ago
Inline HTML5 video makes firefox extremely choppy
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox15 affected, firefox16 affected, firefox17 affected, fennec16+)
People
(Reporter: oyiptong, Unassigned)
References
()
Details
(Keywords: perf)
Playing an inline video makes Firefox very choppy.
The video itself plays at a very low framerate, but Firefox itself becomes very slow and unresponsive
|
||
Comment 1•12 years ago
|
||
Tested device was the Nexus 7, and it looks like with no plugin support they are serving HTML5 video. The frame-rate was pretty bad.
tracking-fennec: --- → ?
status-firefox15:
--- → affected
status-firefox16:
--- → affected
status-firefox17:
--- → affected
|
|
||
Updated•12 years ago
|
Component: Plugins → General
|
|
||
Updated•12 years ago
|
Summary: Inline video makes firefox extremely choppy → Inline HTML5 video makes firefox extremely choppy
|
||
Updated•12 years ago
|
tracking-fennec: ? → 16+
|
||
Updated•12 years ago
|
Whiteboard: DUPEME
|
|
||
Comment 2•12 years ago
|
||
qawanted to see if bug 782327 has made this significantly better. If it has, we should talk about uplifting.
Keywords: qawanted
|
||
Comment 3•12 years ago
|
||
Tested on Nightly 2012-08-27 using the Acer Iconia Tab A500 running Android 3.2. Tested using the URL from the bug with the plugin option set to off in order to receive the HTML5 videos. The videos continue to play very choppy and hangs a lot. I am not seeing more then 2-3 seconds of continues play before the video freezes.
Keywords: qawanted
|
Reporter | |
Comment 4•12 years ago
|
||
The bug looks fixed on a Nexus 7
|
|
Reporter | |
Comment 5•12 years ago
|
||
The video plays smoothly and scrolling is almost buttery smooth.
The Nexus 7 is running Jelly Bean 4.1.1
|
|
||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
|
Assignee | |
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•