OK, I would like to find a workaround for you, while also figuring out what exactly is going wrong. I'll need you to do some experimenting, or if you can give me a link to an example that shows the problem you are experiencing, especially a simplified example using jsfiddle or something similar, that would be great.
Is it possible to check whether the code does get executed, but only after your onload handler is called? Could you try using addEventListener rather than the onload mechanism? Can you try adding a static loading of the loader, just to make sure that use case still works? On Tue, Feb 21, 2023 at 12:12 PM Nikos Katsikanis <nkatsika...@gmail.com> wrote: > Thanks for your quick response, we manage this loading, so it only happens > once; as we have dynamic routes, we want to load it on only some pages. > > On Tuesday, February 21, 2023 at 4:23:39 PM UTC Daniel LaLiberte wrote: > >> The loader has been updated for the 'upcoming' release of v52, but it >> should only have added access to the new version. There have been other >> refactoring changes that conceivably could have affected the code, but I >> see how it could have lost the definition of the global 'google'. >> Moreover, I am not sure I can easily revert this change of the loader, >> since I would have to return to the compilation environment from a couple >> years ago. >> >> The way you are loading the loader, using a constructed async script >> element appended to the body, is significantly different from the typical, >> more static loading via a script tag in the document head. I'm wondering >> if you are using this pattern multiple times in the document, perhaps >> unintentionally. >> >> >> On Tue, Feb 21, 2023 at 6:55 AM Nikos Katsikanis <nkats...@gmail.com> >> wrote: >> >>> I have this code, with type `/// <reference types="google.visualization" >>> />` >>> but google is not recognised: >>> >>> [image: Screenshot 2023-02-21 at 11.55.21.png] >>> >>> -- >>> 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/ee101963-b123-4cbc-90ca-a59039c3f5f3n%40googlegroups.com >>> <https://groups.google.com/d/msgid/google-visualization-api/ee101963-b123-4cbc-90ca-a59039c3f5f3n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> >> >> -- >> >> • Daniel LaLiberte >> >> • SWE >> >> • Cambridge MA >> >> • dlalibe...@google.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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-visualization-api/63a0095c-7a2d-4087-aee3-e40e99f1874dn%40googlegroups.com > <https://groups.google.com/d/msgid/google-visualization-api/63a0095c-7a2d-4087-aee3-e40e99f1874dn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- • Daniel LaLiberte • SWE • Cambridge MA • dlalibe...@google.com <dlalibe...@google.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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJNgLypVXUMAW1CwLm3Crf9UpMpvopa7Cojh5M-XEcN7TA%40mail.gmail.com.
