Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178)

1. The idea of removing an option is fundamentally flawed - nobody is forced to use an option. 2. Any coding in the web environment can lead to 'detrimental effects to the end user’s experience', including javascript itself. 3. I use synchronous XHR after the page has loaded, so then there is absolute no 'detrimental effects to the end user’s experience' - on the contrary. 4. I even use synchronous XHR during the loading of the pages, and I have never noticed any 'detrimental effects to the end user’s experience' - and that is with about ten years of experience. Conclusion: this idea has no ground at all.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/xhr/issues/178#issuecomment-356938683