Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XMLHttpRequest #193

Closed
nhatchett opened this issue Feb 20, 2018 · 3 comments
Closed

XMLHttpRequest #193

nhatchett opened this issue Feb 20, 2018 · 3 comments

Comments

@nhatchett
Copy link

Why are you removing the abilility to execute an XMLHttpRequest syncronously?

I agree that that misuse of this feature can create unresponsive web pages but careful use (i.e. in the pagehide event) enables AJAX based feed back mechanisms to work on some popular yet awkward browsers (i.e. Firefox).

Most sensible web developers are aware that misusing this feature is undesirable and use the asyncronous option. I feel that removing such a feature because of its detrimental effects to the end user's experience is a very poor decision akin to chopping of a childs hand because it does not know how to use it.

I assume the decision is based on the lowest common denominator principle - when a few are morons treat us all like morons.

@annevk
Copy link
Member

annevk commented Feb 20, 2018

Please use navigator.sendBeacon() instead for that purpose. It's not a good reason for synchronous I/O.

Marking this as a duplicate of #20.

@annevk annevk closed this as completed Feb 20, 2018
@nhatchett
Copy link
Author

nhatchett commented Feb 20, 2018 via email

@annevk
Copy link
Member

annevk commented Feb 21, 2018

I removed the experimental label from https://developer.mozilla.org/en-US/docs/Web/API/Navigator/sendBeacon if that's what you're referring to. That was simply out-of-date.

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

No branches or pull requests

2 participants