Gotcha.

Unfortunately, our app doesn't have any public facing pages. I'll see if I 
can setup a test environment or something. Or... would a chrome dev tools 
HAR file be sufficient?

In any case, since v46 seems to be working fine, I feel no more urgency 
around this.

On Tuesday, February 11, 2020 at 12:55:54 PM UTC-5, Daniel LaLiberte wrote:
>
> Hi Jeff,
>
> Your snippet looks fine as it is, but it wouldn't work without the key 
> ingredient, the part that loads the loader.   I expect you are using the 
> new loader at https://www.gstatic.com/charts/loader.js, but what else is 
> going on?  Since you are using jquery, you also must be loading that, but 
> how?  It would be best to point at a web page that does it all, and then I 
> can also see its source code from that same page.
>
> And maybe just switch back to 'current' and all will be resolved.  But 
> elsewhere, someone is having issues with the arrayToDataTable function, so 
> I am open to whatever bizarre issues might come up.
>
>
>
> On Tue, Feb 11, 2020 at 12:32 PM Jeff Johnson <jjoh...@nulogy.com 
> <javascript:>> wrote:
>
>> Hi Dan, thanks for the quick updates! I also appreciate the transparency.
>>
>> Here's the snippet we're using to load google charts: 
>> https://gist.github.com/jmjohnson/3c37f229d36fd79be680283269b0646a
>>
>> $j is jquery v1.9.1
>>
>> We don't have any other kinds of google chart loading setups. I bet 
>> things are working if we were to switch to current again. I'll follow up if 
>> that's not the case.
>>
>> Thanks again for all your help! (and for free no less!)
>>
>> On Tuesday, February 11, 2020 at 9:39:45 AM UTC-5, Daniel LaLiberte wrote:
>>>
>>> Yes, in fact there were a few unannounced updates of v47 last night, and 
>>> another update just now.  I've mostly been modifying the loader, in 
>>> particular, to support more redirects that the old jsapi loader still 
>>> supports.   But along the way, I messed up by updating the loader with a 
>>> version that was out of sync with the Google Charts library itself.  So I 
>>> also redeployed all of v47 last evening.  
>>>
>>> As far as I can see, everything should be working now, but there may be 
>>> a few ways of loading and using Google Charts that I am not aware of that 
>>> may still be causing issues.  Please let me know the details of how you are 
>>> loading Google Charts so I can reproduce the problem, including how you 
>>> load the loader, load packages, and set up callbacks.
>>>
>>>
>>> On Tue, Feb 11, 2020 at 9:23 AM Jeff Johnson <jjoh...@nulogy.com> wrote:
>>>
>>>> Hiya, I just noticed that the "last modified" header on 
>>>> https://www.gstatic.com/charts/loader.js says "Tue, 11 Feb 2020 
>>>> 04:46:35 GMT". Was there an unpublished fix, or other change? This might 
>>>> be 
>>>> causing issues. At least one other poster besides myself appears to be 
>>>> experiencing some kind of exception that is solved by explicitly loading 
>>>> version 46 instead of current.
>>>>
>>>> Here's a small screencap of the exception: 
>>>>
>>>> On Monday, January 6, 2020 at 1:53:02 PM UTC-5, Daniel LaLiberte wrote:
>>>>>
>>>>> The 'current' version of Google Charts is now (within the hour) v47.  
>>>>> Please let us know if you discover problems related to this new release.
>>>>>
>>>>> On Fri, Dec 20, 2019 at 11:24 AM Daniel LaLiberte <dlali...@google.com> 
>>>>> wrote:
>>>>>
>>>>>> As of now, the 'upcoming' version of Google Charts is v47.  This 
>>>>>> release includes a large number of internal cleanups, and a few new 
>>>>>> features:
>>>>>>
>>>>>>    - Add loader setting to enable "safeMode".  
>>>>>>       - When set to true, all charts and tooltips that generate HTML 
>>>>>>       from user-supplied data will sanitize it by stripping out unsafe 
>>>>>> elements 
>>>>>>       and attributes.
>>>>>>    - Add support for the "autoload" and "callback" parameters on the 
>>>>>>    loader, to be backward compatible with the old jsapi loader.
>>>>>>    - For corecharts
>>>>>>       - Handle "zoomDelta" values below 1.0
>>>>>>       - Add "maxTextLines" as a vertical axis option.
>>>>>>    
>>>>>> If all goes well, this 'upcoming' version will become 'current' in 
>>>>>> the first week of January.
>>>>>>
>>>>>> -- 
>>>>>> Daniel LaLiberte 
>>>>>> <https://plus.google.com/100631381223468223275?prsrc=2>
>>>>>> dlali...@google.com   Cambridge MA
>>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> Daniel LaLiberte 
>>>>> <https://plus.google.com/100631381223468223275?prsrc=2>
>>>>> dlali...@google.com   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 google-visualization-api+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/google-visualization-api/86f7c4ed-c792-485a-9a34-9a9e90356432%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/google-visualization-api/86f7c4ed-c792-485a-9a34-9a9e90356432%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>
>>>
>>> -- 
>>> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
>>> dlali...@google.com   Cambridge MA
>>> go/gviz-headcount <https://goto.google.com/gviz-headcount>
>>>
>> -- 
>> 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+unsubscr...@googlegroups.com 
>> <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-visualization-api/949f720d-30b5-4d93-88aa-8469005d1a9c%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-visualization-api/949f720d-30b5-4d93-88aa-8469005d1a9c%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> -- 
> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
> dlali...@google.com <javascript:>   Cambridge MA
> go/gviz-headcount
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/cdf490e7-5f47-41c3-8c88-4a9531473568%40googlegroups.com.

Reply via email to