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 <[email protected]> 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-visualization-api/f54e9562-344b-4ec1-a136-180391f8a9d6%40googlegroups.com > <https://groups.google.com/d/msgid/google-visualization-api/f54e9562-344b-4ec1-a136-180391f8a9d6%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2> [email protected] <[email protected]> Cambridge MA -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMhFdOS6-utVUX3q4zr0HrFUV1CK0QTP0scATRb2QAX6A%40mail.gmail.com.
