New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 611696 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Leaves the project on 2018/03/02
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

crossOrigin attribute blocks loading html5 audio from dataURI

Reported by nederlan...@gmail.com, May 13 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.36 Safari/537.36

Example URL:
https://www.blend4web.com/media/uploads/fe7e44a3-129a-4363-8d2e-16b515735da7/1.html

Steps to reproduce the problem:
1. Create an html document.
2. Create an audio element with crossOrigin attribute set to anonymous.
3. Set base64 encoded Data URI as a source.

What is the expected behavior?
The mediafile should be loaded and should be available for playing.

What went wrong?
The "error" event appears, although the audio file has 200(OK) status in the Network panel.

Did this work before? Yes It worked in 48.0.2564.109, but didn't work in 49.0.2623.75.

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes 

Chrome version: 51.0.2704.36  Channel: beta
OS Version: Ubuntu 15.04
Flash Version: Shockwave Flash 21.0 r0

1) There is also an image element in the example, which is loaded through the same method (dataURI + crossOrigin) and it works. 

2) This works in Firefox both in Ubuntu 15.04 and in Windows 7.

3) This can be related to https://bugs.chromium.org/p/chromium/issues/detail?id=511251. For now it requires to set crossOrigin to "anonymous" to be able to load/play a dataURI audio, but this flag currently breaks the loading.
 
1.html
12.1 KB View Download
Owner: hubbe@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 2 by hubbe@chromium.org, Jul 14 2016

Status: Started (was: Assigned)

Comment 3 by hubbe@chromium.org, Nov 4 2016

Cc: hubbe@chromium.org
Owner: tyoshino@chromium.org
This seems to be an issue with how blink handles origins of DataURIs.
Tyoshino, would this be something you know more about?

Comment 4 by ricea@chromium.org, May 7 2018

Status: WontFix (was: Started)
This became fixed at some point. Closing.

Sign in to add a comment