Question: Deprecated Synchronout XMLHttpRequest #74

thinsoldier opened this Issue Jul 16, 2015 · 4 comments


None yet

2 participants


I recently noticed this in my console on a site I used your history.js with:

Synchronous XMLHttpRequest on the main thread is deprecated because of 
its detrimental effects to the end user's experience.

I'm wondering if this has something to do with your history.js or something in pronto.js

And do you have any tips for someone looking to upgrade from history.min.js version 3.3.0 to the latest version of ajaxify.min.js 5.7.0?

arvgta commented Jul 16, 2015

Hi Thinsoldier!

Yes, it's coming from ajaxify.js in general though I have not succeeded in pin-pointing the origin of the message.

Have tried specifying:

async: true

...explicitly in the central...

$.ajax(), just now.

Unfortunately, that doesn't change a thing.

So, I'm wondering, whether this issue could be it?
Does anyone else have a clue?

When migrating from 3.3.0 to 5.7.0, one obviously has to pay attention to the interface changes.

Cheers and

arvgta commented Jul 19, 2015

Have raised this issue at

Summary / outcome of the thread:

url:"" is being requested with async:false

However, the warning is also generated on e.g. Barz Noble,
therefore ruling out, that it is site specific to

@thinsoldier : The thread has returned with a synthesis
It's due to script src= tags being injected dynamically in the head.

Jake, the moderator at doesn't think there is much that can be done.
Supposedly, this issue will disappear in future jQuery versions.
(in the current version of JQ 3.0 Alpha - it persists)

@arvgta arvgta closed this Jul 27, 2015

Thanks arvgta.

My real problem was that my youtube videos weren't loading. I thought that error had something to do with it. It didn't. I needed to update my youtube code to use version 3 of their api.

I think it won't be hard to combine all of my JS into a single file to avoid the jquery error.

arvgta commented Jul 28, 2015

That's great! Then we'll leave this issue closed... Best of luck!

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