- From: Kagami Sascha Rosylight <notifications@github.com>
- Date: Sun, 21 May 2017 08:55:46 -0700
- To: whatwg/xhr <xhr@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 21 May 2017 15:56:21 UTC
>but together with a more active plan to get rid of this, the deprecation message could still make sense If we want really be aggressive probably browsers *can* forcefully block `n` seconds whenever sync XHR occurs and irritate users so that devs will actively remove it. Not sure browsers *may* do it. 🤔 -- 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/20#issuecomment-302945340
Received on Sunday, 21 May 2017 15:56:21 UTC