- From: <bugzilla@jessica.w3.org>
- Date: Tue, 25 Feb 2014 08:54:18 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24790 --- Comment #3 from Chris <fubizitch@yahoo.com> --- This is on the console of the newest development version of Firefox (Nightly): "Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help http://xhr.spec.whatwg.org/" I'm not confused, but maybe the Firefox developers are? Using Sync XHR is similar to clicking on a link to go to another page or submitting a form, except that the site doesn't have to refresh and reload everything. Why would this be used only by the inexperienced programmer? For example, a login script or a save to the server before the user loses the displayed information. It would be a pain to tell all other scripts to not respond while processing this script, or to place a huge box over the interface (which wouldn't prevent the nefarious users from making their own javascript calls via the url bar). Sometimes there is GOOD reason to lock an interface until a process either confirms or rejects a server call. There are other instances where we would need a sync call too, like triggering a script before telling a video or audio file to play. Loading an HTML5 media file on a mobile device generally requires the user to actually click on a button that then triggers the .play() or .load() function, and if you use an ASYNC call for this, the media file simply won't load. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 25 February 2014 08:54:20 UTC