![]() The reason I doubt that the other comments had the same cause is that they didn't include the "Synchronous XHR in page dismissal" message I'm assuming they didn't just forget to copy that, since it's pretty distinctive.So I was going through my first webview tutorial to learn the basics and see how javascript works. ![]() As for why you were seeing it a little before, but now are seeing it a lot, I would guess that either more of your users have the latest Chromium now, or for whatever reason your application is generating events more often than it used to so it's more likely to have some unsent ones in the queue at page unload time. ![]() We'll have to think about the best way to adapt. We suspected that browsers might stop supporting this kind of thing at some point, but we hadn't seen this specific change in Chrome, so thanks for that. The intention is to minimize any loss of analytics events, so that your dashboard is as up to date as possible, without requiring you to use a very short event flush interval. if the flush task has not yet fired), and if so, it attempts to send them using a synchronous HTTP request (if it were async, it would have no chance to complete before the page got unloaded). It checks if there are any events waiting to be sent (i.e. There is a beforeunload handler that is called whenever the current page is about to go away. That normally happens in an asynchronous flush task that is triggered by setTimeout, and the request itself is also async. Requests to are for posting analytics events (such as the ones generated by variation). There are a few different types of request involved here, so I don't think what you're seeing is necessarily related to what the other users were seeing, but it's relevant.įirst, calling variation doesn't do any I/O at all the method is synchronous in that it returns a value right away without deferring any actions, not because it performs a synchronous HTTP request (or any request). Makes me wonder if this a Chrome specific issue? Some sort of deterrent from the dev team to stop using synchronous XHR? There is a related commit in Chromium from 3 months ago - Thanks for looking into this. This makes me think this isn't actually affecting any users who actually stay on the page, only those who bounce before the variation call has completed. If everything loads, and then I navigate away, no error is thrown. According the README this is a synchronous request, and the only way I can actually recreate this is by trying to refresh the page before the request has completed, which then throws the above error in the console before reloading the page. The client code is present on all our pages and we make one call after initialising the client on the frontend: val = client.variation(key, null).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |