Open
Bug 1084564
Opened 11 years ago
Updated 3 years ago
Pretty much all of our <video> reftests fail on Android
Categories
(Core :: Audio/Video: Playback, defect)
Core
Audio/Video: Playback
Tracking
()
NEW
People
(Reporter: dholbert, Unassigned)
References
Details
While working on bug 624647, I noticed that my reftests with <video src="something.webm"> fail on Android & B2G, with the <video> element just being blank.
It looks like this is a known issue -- nearly all the reftests in webm-video/reftest.list and ogg-video/reftest.list are marked as "skip-if(Android||B2G)" or "fails-if(Android||B2G)". But there's no bug filed to cover them. (A few are labeled as "bug 773482", but that's a generic tracking bug for B2G failing reftests; not video-specific.)
I'm filing this bug to cover this <video> issue on B2G & Android, so that (a) I have a useful bug number to label my B2G/Android reftest-failures with (in my new tests), and (b) hopefully someone can come along, see what's going on, and fix this.
Reporter | ||
Updated•11 years ago
|
Blocks: b2g-reftest
Reporter | ||
Comment 1•11 years ago
|
||
I pushed a patch to mention this bug number in webm-video/reftest.list & ogg-video/reftest.list:
https://hg.mozilla.org/integration/mozilla-inbound/rev/9f2c5c03252b
I just mentioned the bug number once, at the top of the file, to avoid cluttering up the file too much (by e.g. adding it in a comment at the end of every single line).
> (A few are labeled as "bug 773482", but that's a generic tracking bug
> for B2G failing reftests; not video-specific.)
I also removed these ^ few generic labels from these tests, in this cset.
Keywords: leave-open
Reporter | ||
Updated•11 years ago
|
Keywords: leave-open
Updated•10 years ago
|
Component: Audio/Video → Audio/Video: Playback
Reporter | ||
Comment 3•9 years ago
|
||
[dropping B2G from bug summary, per bug 1306391]
Summary: Pretty much all of our <video> reftests fail on B2G & Android → Pretty much all of our <video> reftests fail on Android
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•