Skip to content

Prevent implicit return of window.URL function - #576

Merged
aFarkas merged 1 commit into
aFarkas:gh-pagesfrom
outdooricon:master
Sep 17, 2016
Merged

aFarkas merged 1 commit into
aFarkas:gh-pagesfrom
outdooricon:master

Conversation

@outdooricon

Copy link
Copy Markdown
Contributor

This prevents the implicit return of window.URL's constructor instead of a simple boolean value for usermedia-core's test. This is important because the polyfiller looks to see if test is a function, and if so calls it. The recently released Chrome 53 doesn't allow direct calls to the URL constructor anymore and will throw an error if called directly. So now a lot of people are seeing webshim break and the further load of their JS stack halt.

It looks like the call to URL's constructor has been occurring for a little while now but was hidden because the existence of window.URL is still being verified, even though it was also being erroneously called.

@pherris

pherris commented Sep 16, 2016

Copy link
Copy Markdown

👍

@aFarkas
aFarkas merged commit f995ee1 into aFarkas:gh-pages Sep 17, 2016
@eraserqueen

Copy link
Copy Markdown

Can we get this fix in a new release please?

@aFarkas

aFarkas commented Nov 11, 2016

Copy link
Copy Markdown
Owner

@eraserqueen
I will do so. Give me this weekend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants