-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
webpack/uglify-es depend on new JS frontend bindings #533
Comments
Best guess for the actual error is
|
It's coming from |
I think the change needs to occur in |
One other possibility is |
That didn't seem to help. For the record, we did this, which is probably on second thought a no-op:
|
Maybe also |
Not fixed by this either:
|
Nor this:
|
Issue 533 no longer seems to impact use of the Citi site, evidently due to changes on the Citi side. I was able to login to my account, pay my bill and print a PDF of the transaction with no problem this morning. |
After much analysis I have concluded the issues with current webpack (and uglify, when used to build the front end package) are due to the new front-end bindings introduced in Firefox 51. The symptom is usually
this is undefined
in the JavaScript console, seeangular/angular-cli#9340 (comment)
Currently affected test sites:
https://www.citibank.com (at account login)
https://cloud.google.com/blog (doesn't work hardly at all)
However, it's probable this affects lots of sites and is likely to affect others as they upgrade their front end blobs.
The new front end bindings are https://bugzilla.mozilla.org/show_bug.cgi?id=1263355
This is a huge undertaking. It isn't clear which part fixes the problem.
The text was updated successfully, but these errors were encountered: