@simone and blackat

My guess is you'll have some javascript exceptions in the console, which should start to indicate what is broken. 
Please share those and probably also share the line of code that is triggering the error?

It's possible we introduced a new javascript property/object that conflicts with something you were doing.
Additionally, if you can find a case where I can reproduce a page failing consistently, that'd be helpful.

Could this be the same issue that is breaking our Proxy script?  https://bugs.chromium.org/p/chromium/issues/detail?id=615084 

Potentially, if so then ` --disable-out-of-process-pac  ` should fix the problem.

@paul there is an open issue,  bug 609848 , for a known regression that is causing massive problems for users of older versions of the 'xstyle' JS library for working with CSS; the symptom is similar to what's described here (shows up as a "ReferenceError" in the javascript console) 

the change that introduced the bug in Chrome 51 is already reverted in canary builds but is pending review for merge into to current stable channel, anything you can do to speed that along would be very much appreciated by the many engineers otherwise working on patches to both SaaS both also software deployments that are affected

Thanks philip. I bet you're right and its 609848

I'll wait a little bit before I dupe into that, but that'll likely be the resolution. 

Marking as M51 Stable blocker as this issue is reported by outside users. Please feel free to remove "ReleaseBlock-Stable" if you think otherwise. 

We're cutting M51 Stable RC early next week on Tuesday afternoon. pls make sure to land the fix and get it merged before then.

> My guess is you'll have some javascript exceptions in the console, which should start to indicate what is broken. 
> Please share those and probably also share the line of code that is triggering the error?

The only exception I've observed is the ReferenceError that signals the problem itself when I try to access a variable, but clearly something must have gone wrong before that. Other than that, it's hard to identify a specific line of code where things have gone wrong - I assume it's somewhere in the huge minified libraries that I'm using but haven't written.

Hi, I'm having a similar problem.

Console is printing out the following:

    undefined:1 Uncaught (in promise)

For me this is happening when trying to export an image generated from "plotly.js". https://plot.ly/javascript/static-image-export/

I have attached a file which will reproduce the issue.

Hope this helps.

Deleted: chrome-51.0.2704.63.html 1.4 KB

chrome-51.0.2704.63.html 1.4 KB View Download

paulirish@, Would you mind providing an update on this.

Per comment #5, this is a dupe of 609848 which is fixed and merged to M51. Hence, we're moving forward with M51 release.
 
paulirish@, please let us know ASAP if there is anything else is still pending here. Thank you.

AFAIK, this is a dupe of 609848

Hi,
We are also facing same JS broken issue; We are using the JQuery ("webkitMatchSelector" and "querySelectAll"; these functions are breaking after upgrade the latest version of chrome 51.0.2704.63 ).

please let us know the update for this. Thank you.

As per c#11 and c#12, this should be fixed in the next release of M51. Please update if that does not seem to be the case. 

This patch is now pushing out to stable channel in version 51.0.2704.79 for Desktop (Win,Mac & Linux).

>  We are using the JQuery ("webkitMatchSelector" and "querySelectAll"; these functions are breaking after upgrade the latest version of chrome 51.0.2704.63 ).

This is a different bug. However I believe that if you update your jQuery version, it is fixed there.