google.visualization.Query times out in Microsoft Edge

150 views
Skip to first unread message

Amy Finkbiner

unread,
May 12, 2020, 8:16:22 PM5/12/20
to Google Visualization API
Hi!  Calls to "new google.visualization.Query(URL);" started failing in Microsoft Edge sometime in the last few days.  (I'm not sure exactly when; the issue was reported by a user as "It worked the other day, but not today.")  Has anyone else noticed this problem?

I have a number of pages that are affected, but you can also reproduce it at the official Google site:  Visit https://developers.google.com/chart/interactive/docs/spreadsheets and navigate to the section "Here's a complete example:"
  • Google Chrome displays a bar chart as expected
  • Microsoft Edge has a blank space, and after 30 seconds displays an alert box: "Error in query: Request timed out"
I'm running Edge 44.18362.449.0, which was released in Nov 2019, so I'm assuming whatever changed is on the API end.

Thanks,
Amy

Amy Finkbiner

unread,
May 14, 2020, 7:34:49 AM5/14/20
to Google Visualization API
Here's some minimal reproduction code:

<html>
  <head>
    <script type="text/javascript" src="https://www.gstatic.com/charts/loader.js"></script>
    <script type="text/javascript">
      google.charts.load('current', { callback: displayCount });
      function displayCount() {
        var myDiv = document.getElementById('myDiv');
        var query = new google.visualization.Query(
        query.send(
          function (response) {
            if (response.isError()) {
              alert('Error in query: ' + response.getMessage() + ' ' + response.getDetailedMessage());
            }
            var dataTable = response.getDataTable();
            myDiv.innerHTML = "Read " + dataTable.getNumberOfRows() + " rows of data.";
          })
      }
    </script>
  </head>
  <body>
    <div id="myDiv">This should be replaced by a count.</div>
  </body>
</html>

Amy Finkbiner

unread,
May 14, 2020, 7:35:36 AM5/14/20
to Google Visualization API
For anyone who finds this by searching, you can work around the issue by calling google.charts.load('47') instead of google.charts.load('current').

Daniel LaLiberte

unread,
May 14, 2020, 10:47:47 AM5/14/20
to Google Visualization API
Thanks for your post(s) Amy.  I can reproduce the problem as well, and we are investigating the cause.  There appears to be some incompatibility with how Edge supports the features we are using in the Query call and response.

On Thu, May 14, 2020 at 7:35 AM Amy Finkbiner <amy.fi...@gmail.com> wrote:
For anyone who finds this by searching, you can work around the issue by calling google.charts.load('47') instead of google.charts.load('current').

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/f54e9562-344b-4ec1-a136-180391f8a9d6%40googlegroups.com.


--

Amy Finkbiner

unread,
May 14, 2020, 8:05:59 PM5/14/20
to Google Visualization API
Thanks!

Matthew Oberdier

unread,
May 29, 2020, 2:20:14 PM5/29/20
to Google Visualization API
Worked. Thanks

Joseph Janos

unread,
Jul 27, 2020, 3:38:12 PM7/27/20
to Google Visualization API
Thanks, Amy for the solution! It works!

Daniel,

I assume you tested this bug on various platform: this is NOT MS Edge specific. I ran into this bug on a pure Google platform. (Chrome, Google Drive.)

Joseph


On Thursday, May 14, 2020 at 4:47:47 PM UTC+2, Daniel LaLiberte wrote:
Thanks for your post(s) Amy.  I can reproduce the problem as well, and we are investigating the cause.  There appears to be some incompatibility with how Edge supports the features we are using in the Query call and response.

On Thu, May 14, 2020 at 7:35 AM Amy Finkbiner <amy.fi...@gmail.com> wrote:
For anyone who finds this by searching, you can work around the issue by calling google.charts.load('47') instead of google.charts.load('current').

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.

Daniel LaLiberte

unread,
Jul 27, 2020, 4:04:37 PM7/27/20
to Google Visualization API
Hi Joseph,

Yes, we tested on all the modern browsers.  In fact, a big reason for the change was to accommodate MS Edge.    

The problem now seems to be that some spreadsheet URLs get redirected (perhaps via server-side, so not visible?) which results in failures because the CORS related info is not passed on.  Check your browser's debugger to see what it reports when trying to do the query.  If there is a redirect, use the URL that it redirects to, and you might have better luck.

On Mon, Jul 27, 2020 at 3:38 PM Joseph Janos <jja...@gmail.com> wrote:
Thanks, Amy for the solution! It works!

Daniel,

I assume you tested this bug on various platform: this is NOT MS Edge specific. I ran into this bug on a pure Google platform. (Chrome, Google Drive.)

Joseph

On Thursday, May 14, 2020 at 4:47:47 PM UTC+2, Daniel LaLiberte wrote:
Thanks for your post(s) Amy.  I can reproduce the problem as well, and we are investigating the cause.  There appears to be some incompatibility with how Edge supports the features we are using in the Query call and response.

On Thu, May 14, 2020 at 7:35 AM Amy Finkbiner <amy.fi...@gmail.com> wrote:
For anyone who finds this by searching, you can work around the issue by calling google.charts.load('47') instead of google.charts.load('current').

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/4f7f31f3-d492-49f5-882e-66fee32b8ce7o%40googlegroups.com.

Alexey Leshchenko

unread,
Jul 28, 2020, 7:14:34 AM7/28/20
to Google Visualization API
Hi!

I had the same problem on Chrome and Yandex.Browser.

Access to XMLHttpRequest at 'https://spreadsheets.google.com/d/1Hcc4ay2SZu1gImUljdbTVgw3GEaJrz-7IerNWcZDRzU/gviz/tq?gid=372589317&headers=1&tq=SELECT%20*%20WHERE%20(A%3D%22%D0%A2%D1%8F%D0%B3%D0%B0%D1%87%22)%20AND%20(E%20%3C%3D%2010000000)%20LIMIT%2040&tqx=reqId%3A0' from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Amy's solution worked, though.


On Monday, July 27, 2020 at 11:04:37 PM UTC+3, Daniel LaLiberte wrote:
Hi Joseph,

Yes, we tested on all the modern browsers.  In fact, a big reason for the change was to accommodate MS Edge.    

The problem now seems to be that some spreadsheet URLs get redirected (perhaps via server-side, so not visible?) which results in failures because the CORS related info is not passed on.  Check your browser's debugger to see what it reports when trying to do the query.  If there is a redirect, use the URL that it redirects to, and you might have better luck.

On Mon, Jul 27, 2020 at 3:38 PM Joseph Janos <jja...@gmail.com> wrote:
Thanks, Amy for the solution! It works!

Daniel,

I assume you tested this bug on various platform: this is NOT MS Edge specific. I ran into this bug on a pure Google platform. (Chrome, Google Drive.)

Joseph

On Thursday, May 14, 2020 at 4:47:47 PM UTC+2, Daniel LaLiberte wrote:
Thanks for your post(s) Amy.  I can reproduce the problem as well, and we are investigating the cause.  There appears to be some incompatibility with how Edge supports the features we are using in the Query call and response.

On Thu, May 14, 2020 at 7:35 AM Amy Finkbiner <amy.fi...@gmail.com> wrote:
For anyone who finds this by searching, you can work around the issue by calling google.charts.load('47') instead of google.charts.load('current').

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.

Joseph Janos

unread,
Jul 28, 2020, 8:14:33 AM7/28/20
to Google Visualization API
Hi Daniel,

My Chrome version:
Version 84.0.4147.89 (Official Build) (64-bit)
[An extremely modern browser :-)

My platform:
Ubuntu 18.04.4 LTS

The query test I use is from the Google guide:

If I tried to load 'current' the request times out and in the console I get:

Access to XMLHttpRequest at 'https://docs.google.com/spreadsheets/d/1XWJLkAwch5GXAt_7zOFDcg8Wm8Xv29_8PWuuW15qmAE/gviz/tq?gid=0&headers=1&tq=SELECT%20A%2C%20H%2C%20O%2C%20Q%2C%20R%2C%20U%20LIMIT%205%20OFFSET%208&tqx=reqId%3A0' from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
docs.google.com/spreadsheets/d/1XWJLkAwch5GXAt_7zOFDcg8Wm8Xv29_8PWuuW15qmAE/gviz/tq?gid=0&headers=1&tq=SELECT%20A%2C%20H%2C%20O%2C%20Q%2C%20R%2C%20U%20LIMIT%205%20OFFSET%208&tqx=reqId%3A0:1 Failed to load resource: net::ERR_FAILED
jsapi_compiled_default_module.js:251 Uncaught Error: Error handling Query: XhrHttpError: Request Failed, status=0, url=https://docs.google.com/spreadsheets/d/1XWJLkAwch5GXAt_7zOFDcg8Wm8Xv29_8PWuuW15qmAE/gviz/tq?gid=0&headers=1&tq=SELECT%20A%2C%20H%2C%20O%2C%20Q%2C%20R%2C%20U%20LIMIT%205%20OFFSET%208&tqx=reqId%3A0
    at jsapi_compiled_default_module.js:379
    at e.XD (jsapi_compiled_default_module.js:258)
    at gvjs_ok (jsapi_compiled_default_module.js:261)
    at gvjs_lk (jsapi_compiled_default_module.js:261)
    at gvjs_bk.Nna (jsapi_compiled_default_module.js:260)
    at gvjs_$j (jsapi_compiled_default_module.js:255)

If I replace 'current' with '47' the page loads correctly.

Of course I have no way of knowing whether the two bugs have the same root cause or not but
in this experiment there is no MS technology anywhere

Thanks for looking into this.

Let me know if you need more info / dump  / etc from me in order to reproduce this bug.

Joseph


On Monday, July 27, 2020 at 10:04:37 PM UTC+2, Daniel LaLiberte wrote:
Hi Joseph,

Yes, we tested on all the modern browsers.  In fact, a big reason for the change was to accommodate MS Edge.    

The problem now seems to be that some spreadsheet URLs get redirected (perhaps via server-side, so not visible?) which results in failures because the CORS related info is not passed on.  Check your browser's debugger to see what it reports when trying to do the query.  If there is a redirect, use the URL that it redirects to, and you might have better luck.

On Mon, Jul 27, 2020 at 3:38 PM Joseph Janos <jja...@gmail.com> wrote:
Thanks, Amy for the solution! It works!

Daniel,

I assume you tested this bug on various platform: this is NOT MS Edge specific. I ran into this bug on a pure Google platform. (Chrome, Google Drive.)

Joseph

On Thursday, May 14, 2020 at 4:47:47 PM UTC+2, Daniel LaLiberte wrote:
Thanks for your post(s) Amy.  I can reproduce the problem as well, and we are investigating the cause.  There appears to be some incompatibility with how Edge supports the features we are using in the Query call and response.

On Thu, May 14, 2020 at 7:35 AM Amy Finkbiner <amy.fi...@gmail.com> wrote:
For anyone who finds this by searching, you can work around the issue by calling google.charts.load('47') instead of google.charts.load('current').

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages