Nevermind, it’s a server configuration problem. I have no idea what, or how to locate it, but here’s the deal to anyone else who happens across the problem.
If I use periods, dashes, or an underscore, the file fails to be served. I’ve tried the Chrome debugging tools to no avail, the file and path are correct. I tried adding the preload attribute and it still failed. Only if the file is stripped of these delineators will it work. I haven’t tried spaces, but that’s what I have so far.
Viewing 2 replies - 1 through 2 (of 2 total)
The topic ‘[Plugin: oEmbed HTML5 audio] Player broken in Chrome 18’ is closed to new replies.