Thomas, I believe that pages fetched via http can load resources via https without concern, but not the other way around. In other words, loading secure resources in an insecure page is OK, but loading insecure resources in a secure page would compromise the security of the page. If the Google Charts internal use of https causes problems for anyone, I'm sure we'll hear about it.
Version 43 will be frozen sometime before version 44 is released, but more likely, soon after version 43 is released to production which could be in about 1 month. We hope to start the v43 release cycle this week. Regarding the problem with setting the container style.display to 'none', this will continue to be a problem since Google Charts doesn't know how big your text labels are when you draw a chart unless the chart is being displayed, even if it is invisible (via style.visibility). You should be able to call setOnLoadCallback multiple times, at least with the google.charts.setOnLoadCallback. The answer is less clear with google.setOnLoadCallback. On Mon, Sep 14, 2015 at 8:05 AM, Thomas <[email protected]> wrote: > hi > > *https* >> works, thx. >> > > >> *http* >> would be an asset. some html pages have to use http throughout (e.g., >> > taking account of additional 3rd party libraries). >> > > >> *tooltip.css* >> thx for the info. when will google "freeze" 43 (provide a frozen >> version)? 2015? 2016? an exact >> > answer is not necessary, of course. >> > > >> *"overlap problem"* >> if the stable version draws a line chart while style.display of div is >> 'none' (initially), the line chart will be *okay*. >> if the frozen version draws a line chart while style.display of div is >> 'none' (initially), the line chart will be *NOT okay*: the >> vertical labels overlap (a picture is in this thread, above). >> approach (subject to tests): use style.visibility rather than >> style.display. >> > > >> *besides, another question* >> Is it in order to call setOnLoadCallback several times and draw several >> charts? >> >> -- > 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 post to this group, send email to > [email protected]. > Visit this group at > http://groups.google.com/group/google-visualization-api. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-visualization-api/b41e7e50-ad3b-4d7b-87b5-2fc0aac2a020%40googlegroups.com > <https://groups.google.com/d/msgid/google-visualization-api/b41e7e50-ad3b-4d7b-87b5-2fc0aac2a020%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2> - 978-394-1058 [email protected] <[email protected]> 5CC, Cambridge MA [email protected] <[email protected]> 9 Juniper Ridge Road, Acton 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-visualization-api. To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJOgrCb%3Dh3E2efon%2B74vXK68%2BF5u7SdNL%2B8aR%3DN_TqR-mQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
