As per the link below, synchronous mode for XHR is being deprecated in Firefox.https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest
Here is what document says:
Starting with Gecko 30.0 (Firefox 30.0 / Thunderbird 30.0 / SeaMonkey 2.27), synchronous requests on the main thread have been deprecated due to the negative effects to the user experience.
I wanted to know if Chrome is going to follow this? Would it be safe to use synchronous XMLHTTPReuquest in Chrome extension? (For business reason, it needs to synchronous in my case)
--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/ca7d3728-de2e-4a29-9e6b-596ba7f467c1%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.
Why can't you wait for the success callback and call whatever code that needs to execute after from there?
On Wed, Jun 18, 2014 at 9:46 PM, Milind T <mili...@gmail.com> wrote:
As per the link below, synchronous mode for XHR is being deprecated in Firefox.https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest
Here is what document says:
Starting with Gecko 30.0 (Firefox 30.0 / Thunderbird 30.0 / SeaMonkey 2.27), synchronous requests on the main thread have been deprecated due to the negative effects to the user experience.
I wanted to know if Chrome is going to follow this? Would it be safe to use synchronous XMLHTTPReuquest in Chrome extension? (For business reason, it needs to synchronous in my case)
--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/43667c8e-bbc5-40d5-95e4-ec76f70dbc27%40chromium.org.
Sorry I don't follow why you couldn't
Sent from my iPhone
I am looking forward to use synchronous XHR in Webrequest.beforeWebRequest callback. I have business logic that requires XHR response before current WebRequest could be allowed or cancelled. I can't really use success callback for this purpose.--
On Thursday, June 19, 2014 10:33:35 AM UTC+5:30, Marc Fawzi wrote:Why can't you wait for the success callback and call whatever code that needs to execute after from there?On Wed, Jun 18, 2014 at 9:46 PM, Milind T <mili...@gmail.com> wrote:
--As per the link below, synchronous mode for XHR is being deprecated in Firefox.https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest
Here is what document says:
Starting with Gecko 30.0 (Firefox 30.0 / Thunderbird 30.0 / SeaMonkey 2.27), synchronous requests on the main thread have been deprecated due to the negative effects to the user experience.
I wanted to know if Chrome is going to follow this? Would it be safe to use synchronous XMLHTTPReuquest in Chrome extension? (For business reason, it needs to synchronous in my case)
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/ca7d3728-de2e-4a29-9e6b-596ba7f467c1%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/76d6fdce-ff79-4c69-a6d2-419213664b2c%40chromium.org.
--
You received this message because you are subscribed to the Google Groups "Chromium-Extensions-Announce" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.
To post to this group, send email to chromium-extensions@chromium.org.
Visit this group at https://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/a4a42c80-38a2-40ff-8b2e-4a2941de9b20%40chromium.org.