https://www.w3.org/Bugs/Public/show_bug.cgi?id=24790
Bug ID: 24790
Summary: "Developers must not pass false for the async ar..."
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: XHR
Assignee: ann...@annevk.nl
Reporter: fubizi...@yahoo.com
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
This is a HORRIBLE change! Do you realize how many sites rely on async =
false?? This is a necessary thing to use when you don't want the user to be
triggering other scripts (i.e. by clicking on a screen button) while waiting
for a response.
You guys seriously need to rethink deprecating this! Best practices aside, it
should be up to the developer whether or not to piss off users by freezing the
screen until code is executed. Developers will still do this, the only
difference is that it's going to be a pain in the ass to accomplish what is now
very easy to do by using async = false.
PLEASE RECONSIDER!
http://xhr.spec.whatwg.org/#sync-warning
[[
Developers must not pass false for the async argument when the JavaScript
global environment is a document environment as it has detrimental effects to
the end user's experience. User agents are strongly encouraged to warn about
such usage in developer tools and may experiment with throwing an
"InvalidAccessError" exception when it occurs so the feature can eventually be
removed from the platform.
]]
--
You are receiving this mail because:
You are on the CC list for the bug.
