Skip to content

Request onRequest with async: false fires too late in webkit/trident #2317

DimitarChristoff opened this Issue Mar 1, 2012 · 2 comments

2 participants

MooTools member

The request fires on time, we just have it in the wrong place as it seems that webkit won't allow DOM updates once the xhr object exists with async...

it looks as if as soon as the xhr object is created with async: false, webkit locks the UI thread for DOM manipulations so that the onRequest DOM update never arrives. It does run the callback but the visual update does not happen until the UI thread is unlocked. in the test you can query back the html property of the element and it is correct, although it's not so on-screen.

possible solution would be to move the fireEvent further up before the - what downsides can there be? I suppose if setRequesHeaders fails, it's not nice to have dispatched the onRequest before the onException - though I see little options...

works as expected in gecko.

update also fails in IE9

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

afoeder commented Mar 1, 2012

can confirm in Chrome (17.0.963.56 m); @ IR9 even worser with staying the first alert() while the three seconds.

MooTools member

this does not fix it even though the request fires before the, the function does not actually update the DOM until the response arrives.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.