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

Issue 597315 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug



Sign in to add a comment

MR extension break Shaka by setting global variables

Project Member Reported by yini...@chromium.org, Mar 23 2016

Issue description

Version: 51.0.2687.0
OS: all

all videos are not loaded in shaka player http://shaka-player-demo.appspot.com/

What steps will reproduce the problem?
(1) navigate to http://shaka-player-demo.appspot.com/
(2) load any video, e.g "Car" (YT DASH Test) -- MP4
(3) click Load Stream button

What is the expected output?
video plays normally

What do you see instead?
no video is played. console error is as attached.
base.js:413 goog.require could not find: shaka.player.DashVideoSource


Please use labels and text to provide additional information.

 
Screen Shot 2016-03-23 at 10.43.39 AM.png
133 KB View Download
Status: ExternalDependency (was: Assigned)
Summary: MR extension break Shaka by setting global variables (was: all videos are not loaded in shaka player )
This is not a Shaka bug.  See b/27777185.
Cc: ppergame@chromium.org vadimgo@chromium.org amp@chromium.org
Cc: ddorwin@chromium.org
Cc: joeyparrish@chromium.org
Owner: amp@chromium.org
Adam, please close when the fix from Vadim has been cherry-picked to 50.  Thanks!
I just confirmed that this also breaks Shaka as far back as Chrome 47 on Android.

Any update on pushing a fix?  From what I can tell, it seems that this shouldn't require an actual update to Chrome.  See https://github.com/google/shaka-player/issues/311#issuecomment-203088835

Comment 6 by amp@chromium.org, Mar 29 2016

Components: Blink>PresentationAPI
Labels: M-50
The MR extension started experiments in Chrome 50.  Prior to that, it was only possible to get MR enabled by turning on the appropriate flag and therefore not a concern that needs to be fixed in any version prior to Chrome 50.

The fix will not require a Chrome push, but our component extension releases are tied to Chrome releases and we don't plan on updating anything older than the version for Chrome 50.

We are waiting for one other change to land in Chrome and will then update our extension for Chrome 50 after that.
I don't have any flags enabled on Android as far as I know.  Why do I have this issue on Chrome 47 on Android?  What flag should I check for?

Comment 8 by amp@chromium.org, Mar 29 2016

Owner: vadimgo@chromium.org
Sorry, I didn't realize this was an Android issue.  I had assumed it was desktop Chrome only.  Is it both, or only Android?

There is a different deployment mechanism for Android (and yes Media Router has been enabled on Android for much longer than on desktop).

Vadim, how is this handled on the Android side?
Cc: avayvod@chromium.org
We probably can't fix Clank < Chrome 50 at this point, but for Chrome 50+ we will need to update

http://www.gstatic.com/eureka/clank50/cast_sender.js
It is both Chrome desktop & Clank.  I just discovered that Clank was affected today.
Vadim, ping; what's the status here?
It should be fixed in clank now, please check.
Owner: joeyparrish@chromium.org
Cc: tdrews@chromium.org
Owner: yini...@chromium.org
Status: Fixed (was: ExternalDependency)
it's verified fixed in both desktop chrome and clank on build 51.0.2704.7

Sign in to add a comment