Re: [visualization-api] Error: Uncaught (in promise) Error: one or more fonts could not be loaded.(...)

Thanks a lot Sergey. It worked. Best... On Thu, Nov 5, 2015 at 9:02 PM, 'Sergey Grabkovsky' via Google Visualization API wrote: > This is a known issue in 1.1. You might be able to use 1.0 instead, but we > recommend that you use frozen 43. You can

Re: [visualization-api] Error: Uncaught (in promise) Error: one or more fonts could not be loaded.(...)

This is a known issue in 1.1. You might be able to use 1.0 instead, but we recommend that you use frozen 43. You can find instructions for loading it here: https://developers.google.com/chart/interactive/docs/library_loading_enhancements#frozen-versions On Thu, Nov 5, 2015 at 10:19 AM Debashis

Re: [visualization-api] Error: Uncaught (in promise) Error: one or more fonts could not be loaded.(...)

Hi Sergey, Since last couple of hours I am observing a similar behaviour. I am working with Bar package from version 1.1. The first chart is displayed correctly without any error. However, when I try to redraw the same chart with different data-set, I am seeing the same error. This was working

[visualization-api] Error: Uncaught (in promise) Error: one or more fonts could not be loaded.(…)

Hi, since today I get this error in my Chrome console: *Uncaught (in promise) Error: one or more fonts could not be loaded.(…)* at Error (native) at Object.QEa.b.fonts.c.WebFont.c.WebFont.load.fontinactive (eval at e (https://www.gstatic.com/charts/loader.js:133:425), :615:189) at J

Re: [visualization-api] Error: Uncaught (in promise) Error: one or more fonts could not be loaded.(...)

Hi Julian, I'm surprised that this behavior changed yesterday, but I've seen something like this before. Are you customizing any fonts? Could you link to a jsfiddle that reproduces the issue? On Fri, Oct 30, 2015 at 2:47 AM Julian Claus wrote: > Hi, since today I get

Re: [visualization-api] Error: Uncaught (in promise) Error: one or more fonts could not be loaded.(...)

Yes, I am using a Google Font. But the rest of my content has the right font. I can provide an URL: http://www.julianclaus.de/langstreckenlauf/diagramme/ 'Sergey Grabkovsky' via Google Visualization API < google-visualization-api@googlegroups.com> schrieb am Fr., 30. Okt. 2015, 15:32: > Hi

Re: [visualization-api] Error: Uncaught (in promise) Error: one or more fonts could not be loaded.(...)

Yes, I am using a Google Font. But the rest of my content has the right font. I can provide an URL: http://www.julianclaus.de/langstreckenlauf/diagramme/ -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To unsubscribe from this

Re: [visualization-api] Error: Uncaught (in promise) Error: one or more fonts could not be loaded.(...)

Yes it works again. Thank you! 'Sergey Grabkovsky' via Google Visualization API < google-visualization-api@googlegroups.com> schrieb am Fr., 30. Okt. 2015 um 19:02 Uhr: > I just did a push of version 43 with the older version of WebFontLoader, > so your issues should go away soon. > > On Fri,

Re: [visualization-api] Error: Uncaught (in promise) Error: one or more fonts could not be loaded.(...)

Cool, thanks a lot, Sergey! Am Freitag, 30. Oktober 2015 17:32:09 UTC+1 schrieb Sergey: > > Hi Julian, > > This appears to be an error with the new version of the WebFontLoader > (1.6.8 and later). I've filed a bug > against them, and >

Re: [visualization-api] Error: Uncaught (in promise) Error: one or more fonts could not be loaded.(...)

Hi Julian, This appears to be an error with the new version of the WebFontLoader (1.6.8 and later). I've filed a bug against them, and hopefully it will be fixed. On Fri, Oct 30, 2015 at 11:25 AM Julian Claus wrote:

Re: [visualization-api] Error: Uncaught (in promise) Error: one or more fonts could not be loaded.(...)

I just did a push of version 43 with the older version of WebFontLoader, so your issues should go away soon. On Fri, Oct 30, 2015 at 12:35 PM Julian Claus wrote: > Cool, thanks a lot, Sergey! > > > Am Freitag, 30. Oktober 2015 17:32:09 UTC+1 schrieb Sergey: > >> Hi