AngularJS issues with latest version of chrome (52)

[Dustin Talk]

Several issues with AngularJS 1.3 and Chrome 52 that did not occur in Chrome 51 (or other browsers Safari / FF).

1.  403 occurs when there is a preflight OPTIONS request prior to DELETE

in v52, Access-Control-Request-Headers: was set to empty string in pre-flight call (OPTIONS) for DELETE request in angularjs web application.

this issue only happening in V52, but not in the previous version.

Also DELETE with preflight call is working in FF/IE/Safari.

A strong suspect is that Access-Control-Request-Headers: was set to empty string in V52, by comparing the headers (Access-Control-Request-Headers: accept) in V51.

First reported by Lao Francis, and confirmed by me.

2.  Slowness in angular when using a deep watch, v52 only

Originally reported anonymously, http://stackoverflow.com/questions/38845230/web-page-become-really-slow-since-chrome-upgraded-to-version-52

It seems that when using a deep watch (docs here: https://docs.angularjs.org/api/ng/type/$rootScope.Scope#$watch ) Chrome seems to hang for a while. Removing this solves the problem.

Could there be a change in how !== works in the javascript engine?

Thanks,

Dustin

[PhistucK]

For each of those issues, you can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.

[Dustin Talk]

Wow, crbug.com is way overload.

Can someone talk to the engineers so the people don't have to? Who's the people person here?

GL

☆PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[PhistucK]

crbug.com is the place to reports bugs as well as performance issues. Just pasting each of the list items you listed into two separate issue would already be enough to get the ball rolling (of course, it is always preferred to have more details).

☆PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.