Closed Bug 941187 Opened 11 years ago Closed 10 years ago

Jplayer audio not detecting native supported media

Categories

(Web Compatibility :: Site Reports, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 887517

People

(Reporter: robvoyle, Unassigned)

References

()

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131112160018

Steps to reproduce:

Jplayer audio wont' work: see
http://www.appreciativeway.com/hope/test.cfm

The player link "Listen to child of the angels" gives default "plugin required"

Researched with members of jplayer community, updated all components still won't work


Actual results:

get the default plugin required but there is no flash plugin in for Firefox


Expected results:

The recording should play as it does on Windows Firefox, or as it does on the Samsung default browser
This strikes me as a bug in JPlayer. Firefox for Android can play mp3 files without Flash. Visiting the file directly shows this http://www.appreciativeway.com/hope/childOfTheAngels-MJessen.mp3
Component: General → Mobile
Product: Firefox for Android → Tech Evangelism
Version: Firefox 25 → Trunk
E/GeckoConsole( 4854): [JavaScript Error: "TypeError: document.getElementById(...) is null" {file: "http://www.appreciativeway.com/hope/test.cfm?audioToPlay=childOfTheAngels-MJessen.mp3" line: 42}]


http://www.appreciativeway.com/jplayer/jquery.jplayer.min.js

The site is using jQuery jPlayer 2.5.0

Halvord/Karl/Mike, is this a known issue with jPlayer?

https://github.com/happyworm/jPlayer/blob/master/jquery.jplayer/jquery.jplayer.js#L249

Can we identify where their detection fails exactly (we can natively play media but they are prompting for either an updated browser and Flash required)?
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → Android
Hardware: x86 → ARM
Summary: Jplayer audio not working on Firefox Samsung Note 3 → Jplayer audio not detecting native supported media
I'm interested specifically in https://github.com/happyworm/jPlayer/blob/master/jquery.jplayer/jquery.jplayer.js#L935-L941. `document.querySelector('audio')` returns null, so that seems to hint that the `this.html.audio.available` test is failing.

Will need to wait until I'm back at my house to debug with the unminifed source over a proxy.
Assignee: nobody → miket
OK, think I have this figured out. They're not doing any kind of UA sniffing to determine Flash vs. HTML5 audio AFAICT (they're using that to determine platform features like volume/fullscreen).

They do a test to determine mp3 support like so: `$.jPlayer.focus.htmlElement.audio.canPlayType('audio/mpeg; codecs="mp3"')` which returns `""`... which looks like Bug #887517.
Depends on: 887517
(to be more clear, I ran that in the console of http://jplayer.org/latest/demo-01-supplied-mp3/, which demonstrates the same problem)
Just confirmed by removing the codec part from https://github.com/happyworm/jPlayer/blob/master/jquery.jplayer/jquery.jplayer.js#L689 and then the audio plays on Firefox for Android (w/o Flash prompt).
Assignee: miket → nobody
Yes, jPlayer feature checks for support using the mediaElement.canPlayType(mime) method.

I have been considering an addition to jPlayer, which dumbs down the whole canPlayType(), where we test for a range of types... Starting with the codecs being given and going down to "audio/mpeg" in a loop.

There was no sensible way for feature detecting for whether the volume controls had any effect, which is why we added the UA check for the platforms.

A side point: In many browsers the codec part seems to be pointless. Some will even say "probably" to a codec=rubbish while saying maybe without the codec part.
Since it might be of use... The problem was originally investigated by Rob and me here:
https://groups.google.com/d/topic/jplayer/apiPxAdK-Zs/discussion
Mark: thanks for contributing :)

Everyone: I don't think this is a valid evangelism issue - it's just a core bug, no? Can't we just close it as a dup?
Yeah, let's close it as a dupe of 887517. Once that's fixed the problematic site will just work.™
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Product: Tech Evangelism → Web Compatibility
Component: Mobile → Site Reports
You need to log in before you can comment on or make changes to this bug.