Google Charts 'upcoming' release of v45.2

865 views
Skip to first unread message

Daniel LaLiberte

unread,
Jun 15, 2017, 3:09:38 PM6/15/17
to Google Visualization API, charts-announce

You can now load Google Charts version '45.2' by loading 'upcoming'.  Please test this version and let us know if you experience any new problems.


At this time, 'current' is still '45.1'.  You can continue to load version '45' or '45.1' by specifying one of those versions.

Anticipated production release date: June 28

  On this date, loading 'current' or 'upcoming' will load '45.2'. 

This version includes a few bug fixes and many changes that involve internal refactoring, particularly in how options are processed, but there should be no visible changes.


Summary of changes for v45.2:


  • Corecharts

    • Added tooltip.boxStyle options: e.g.

 'tooltip': {

   'boxStyle': {

       'stroke': '#b2b2b2',  'strokeOpacity': 1,  'strokeWidth': 1.5,

       'fill': 'white',  'fillOpacity': 1,

       'shadow': {  'radius': 1, 'opacity': 0.2,  'xOffset': 0,  'yOffset': 2 }

   }}

    • Fix AreaChart legend items to use areaOpacity option.

    • Fix infinite loop when formatted domain values are (incorrectly) numeric.

  • Table

    • Fix paging buttons.

    • Add column type to header cell classlist.

    • Respect column property.

    • Fix accessibility labels when sorting is enabled.

  • Gantt

    • Fix selection object to include row index.


--

Hartmut Gunther

unread,
Jun 16, 2017, 5:04:07 AM6/16/17
to Google Visualization API, charts-...@google.com
Thanks Daniel. Was excited about the tooltip box style and tried to integrate it into my chart, however can't seem to have the tooltip "textStyle" and "boxStyle" working at the same time. If you delete one then the other works?? Any ideas

thanks
Hartmut


Katia Caprarelli

unread,
Jun 16, 2017, 6:05:18 AM6/16/17
to Google Visualization API, charts-...@google.com

Since this morning 16 of june 2017 my application displayed a bug with the combobox using Chrome or IE
After a long debug we realized there should be a conflict between the two libraries : ExtJs 4.07 and Google Chart upcoming release .
changing the google loader in : google.charts.load('44', {............}) //last stable release it start working again

I hope it will be fixed asap

Message has been deleted

Ray Thomas

unread,
Jun 17, 2017, 11:22:49 AM6/17/17
to Google Visualization API, charts-...@google.com
I tested 'upcoming' at https://jsfiddle.net/brisray/fux0vgLm/ and http://hmsgambia.org/crewlist5.htm with no problems.

Unlike Hartmut I had no problems with using tooltip: with both boxStyle: and textStyle: together - https://jsfiddle.net/brisray/fux0vgLm/1/

Maybe a missing comma when adding the new block?

Ray

Hartmut Gunther

unread,
Jun 17, 2017, 9:40:52 PM6/17/17
to Google Visualization API, charts-...@google.com
Thanks for that Ray. Those pesky commas.

However, and this may be a question for Danial...

If you have a tooltip that contains amounts of text that exceed the screen width - it get truncated. If however you turn on isHtml:true then you get a wrap aound effect and all text is displayed. However if isHtml:true  is set the you then loose all the nice  boxStyle formatting. It appears to me then, that you have to choose one or the other.
Just checking whether this is in fact the case.

Hartmut

Daniel LaLiberte

unread,
Jun 18, 2017, 1:22:56 PM6/18/17
to Google Visualization API, charts-announce
Yes, the boxStyle only applies to the non-html tooltip.  But I believe you can modify the style of the html tooltip with your own CSS.

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
 To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/1e9750fa-b24b-44e0-b58c-6e329cbfe678%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Daniel LaLiberte

unread,
Jun 26, 2017, 11:12:03 AM6/26/17
to Google Visualization API, charts-announce
I have now released version 45.2 as 'current'.   (Note, this is a couple days earlier than what I had announced, but there were no problems related to this new version, other than what appear to be uses of different version simultaneously.)

If you need to keep using version 45.1, switch your version from 'current' to '45.1', but also, let us know why you are doing so, assuming you have found a problem.

On Sun, Jun 18, 2017 at 1:22 PM, Daniel LaLiberte <dlali...@google.com> wrote:
Yes, the boxStyle only applies to the non-html tooltip.  But I believe you can modify the style of the html tooltip with your own CSS.
On Sat, Jun 17, 2017 at 9:40 PM, Hartmut Gunther <ha...@nutregy.com.au> wrote:
Thanks for that Ray. Those pesky commas.

However, and this may be a question for Danial...

If you have a tooltip that contains amounts of text that exceed the screen width - it get truncated. If however you turn on isHtml:true then you get a wrap aound effect and all text is displayed. However if isHtml:true  is set the you then loose all the nice  boxStyle formatting. It appears to me then, that you have to choose one or the other.
Just checking whether this is in fact the case.

Hartmut


On Sunday, 18 June 2017 01:22:49 UTC+10, Ray Thomas wrote:
I tested 'upcoming' at https://jsfiddle.net/brisray/fux0vgLm/ and http://hmsgambia.org/crewlist5.htm with no problems.

Unlike Hartmut I had no problems with using tooltip: with both boxStyle: and textStyle: together - https://jsfiddle.net/brisray/fux0vgLm/1/

Maybe a missing comma when adding the new block?

Ray

--
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.
--

Alan Littleford

unread,
Jun 26, 2017, 11:53:47 AM6/26/17
to Google Visualization API, charts-...@google.com
The change seems to have broken bubble chart colors. When using column 3 to determine colors and having only text entries in it all used to work fine. As of 8:20 or so this morning bubble colors all became transparent.

Same thing at https://developers.google.com/chart/interactive/docs/gallery/bubblechart

Going back to 45.1 solved th problem.

Tnx
Alanl

Daniel LaLiberte

unread,
Jun 26, 2017, 11:56:54 AM6/26/17
to Google Visualization API, charts-announce
OK thanks.  I will probably revert very soon.  I'm allowing a little more time for more people to notice problems.

--
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+unsub...@googlegroups.com.

To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/757f6235-fae1-4486-bca8-edb38f02fa89%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Jean-Rémi Delteil

unread,
Jul 3, 2017, 6:33:37 AM7/3/17
to Google Visualization API, charts-...@google.com
Hi Daniel,

The v45.2 doesn't appear to break anything for us, it even fix the pagination buttons for the Table chart.
This remind me that it's really difficult and not straightforward to get the current page number. I would find really really useful to have a mean to get this info.

An other pain point currently is about all the SVG charts: they don't have the viewBox attribute.
This attribute allows the SVG to behave nicely in all browsers !!
Kind of like a box, or an image, allowing us to have a responsive design.

I currently use a sort of hack to apply this attribute on SVG charts (like PIE) and it displays really nicely !
I will share an example when I can.

Cheers !

Jean-Rémi

Daniel LaLiberte

unread,
Jul 3, 2017, 2:48:32 PM7/3/17
to Google Visualization API, charts-announce
Thanks for your feedback about v45.2, Jean-Rémi.

A method to get the current page number should be easily doable.  I'll look into it.

I don't know anything about the viewBox attribute, or how much work it would be to add it.  If it is just about specifying info that is already available, it should be relatively easy to add.  Your hack to add it will be useful as a model to follow.

I've been trying to track down the error with the missing BubbleChart colors in v45.2, and it turns out there is a conflict involving 3 different ways of fixing it, each of which causes other problems, so this is getting more interesting.  I should be able to work it out though.


--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/e8234665-0d0f-4166-ab3f-d0df85493850%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Fabien Denni

unread,
Jul 5, 2017, 4:28:30 PM7/5/17
to Google Visualization API, charts-...@google.com
Hello there, 

Does anybody noticed that charts/graphs have completely changed in appearance since a month on google sheets? We can't present them since and I deeply wish to not go through them all and getting back something clean.
This has affected all my charts on different sheets.

Any information would be very appreciated,
Thanks

On Monday, 3 July 2017 14:48:32 UTC-4, Daniel LaLiberte wrote:
Thanks for your feedback about v45.2, Jean-Rémi.

A method to get the current page number should be easily doable.  I'll look into it.

I don't know anything about the viewBox attribute, or how much work it would be to add it.  If it is just about specifying info that is already available, it should be relatively easy to add.  Your hack to add it will be useful as a model to follow.

I've been trying to track down the error with the missing BubbleChart colors in v45.2, and it turns out there is a conflict involving 3 different ways of fixing it, each of which causes other problems, so this is getting more interesting.  I should be able to work it out though.

On Mon, Jul 3, 2017 at 6:33 AM, Jean-Rémi Delteil <jeanremi...@gmail.com> wrote:
Hi Daniel,

The v45.2 doesn't appear to break anything for us, it even fix the pagination buttons for the Table chart.
This remind me that it's really difficult and not straightforward to get the current page number. I would find really really useful to have a mean to get this info.

An other pain point currently is about all the SVG charts: they don't have the viewBox attribute.
This attribute allows the SVG to behave nicely in all browsers !!
Kind of like a box, or an image, allowing us to have a responsive design.

I currently use a sort of hack to apply this attribute on SVG charts (like PIE) and it displays really nicely !
I will share an example when I can.

Cheers !

Jean-Rémi

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.



--

Daniel LaLiberte

unread,
Jul 5, 2017, 5:23:59 PM7/5/17
to Google Visualization API, charts-announce
HI Fabien,

The Google Sheets team has changed their implementation of charts that are displayed on top of Sheets.  They are reimplementing many of the same options as Google Charts, but not necessarily all, and not in the same way, and perhaps this difference is what you are seeing.  Google Charts has remained mostly the same, and if you can draw your chart by fetching data from a sheet, it should look the way it used to.  Let me know if this is not what you are talking about.

BTW, I have not yet updated the 'current' version to be 45.2 (since I needed to fix a bug), but I will be doing that tomorrow. 


On Wed, Jul 5, 2017 at 4:28 PM, Fabien Denni <fabien...@framestore.com> wrote:
Hello there, 

Does anybody noticed that charts/graphs have completely changed in appearance since a month on google sheets? We can't present them since and I deeply wish to not go through them all and getting back something clean.
This has affected all my charts on different sheets.

Any information would be very appreciated,
Thanks

On Monday, 3 July 2017 14:48:32 UTC-4, Daniel LaLiberte wrote:
Thanks for your feedback about v45.2, Jean-Rémi.

A method to get the current page number should be easily doable.  I'll look into it.

I don't know anything about the viewBox attribute, or how much work it would be to add it.  If it is just about specifying info that is already available, it should be relatively easy to add.  Your hack to add it will be useful as a model to follow.

I've been trying to track down the error with the missing BubbleChart colors in v45.2, and it turns out there is a conflict involving 3 different ways of fixing it, each of which causes other problems, so this is getting more interesting.  I should be able to work it out though.

On Mon, Jul 3, 2017 at 6:33 AM, Jean-Rémi Delteil <jeanremi...@gmail.com> wrote:
Hi Daniel,

The v45.2 doesn't appear to break anything for us, it even fix the pagination buttons for the Table chart.
This remind me that it's really difficult and not straightforward to get the current page number. I would find really really useful to have a mean to get this info.

An other pain point currently is about all the SVG charts: they don't have the viewBox attribute.
This attribute allows the SVG to behave nicely in all browsers !!
Kind of like a box, or an image, allowing us to have a responsive design.

I currently use a sort of hack to apply this attribute on SVG charts (like PIE) and it displays really nicely !
I will share an example when I can.

Cheers !

Jean-Rémi

--
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 post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.



--

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.

Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/eb36c4f3-c396-40d0-a7b0-f51a038ff11e%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--

Daniel LaLiberte

unread,
Jul 6, 2017, 1:08:14 PM7/6/17
to Google Visualization API, charts-announce
As mentioned in my previous reply, I just made 'current' be the updated 45.2, the same as 'upcoming'.  Please post if you notice any more problems.

--

Ariel Falduto

unread,
Jul 6, 2017, 3:19:49 PM7/6/17
to Google Visualization API, charts-...@google.com
Hi Katia, I have the same problem here with ExtJS and is very weird ... for example the Ext.XTemplate object for some reason instead of returning an array is returning an object from jsapi_compiled_format_module, my workaround was to set charts version to 45.1. Also I’m having this problem only in chrome.

Daniel LaLiberte

unread,
Jul 6, 2017, 4:10:07 PM7/6/17
to Google Visualization API, charts-announce
Ariel and Katia, if you could point me at an example page using ExtJS with Google Charts that shows this problem, I'd be happy to look into it.  Otherwise, I don't have much of a clue about what could be going wrong.  I thought I read somewhere that newer versions of ExtJS might also resolve the conflict. 

--
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+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/bb57a7a4-6f11-4c39-8877-1ddc555720d2%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Daniel LaLiberte

unread,
Jul 6, 2017, 4:13:43 PM7/6/17
to Google Visualization API, charts-announce
DaxAll writes about the conflict with ExtJS 4.07: https://github.com/google/google-visualization-issues/issues/2507 

To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.
--

Ariel Falduto

unread,
Jul 6, 2017, 10:04:46 PM7/6/17
to Google Visualization API, charts-...@google.com, Esteban Picone
Hi Daniel, please see the following example to reproduce the issue with ‘current’ version:

Also you can see that works fine with ’45.1’
To post to this group, send email to google-visua...@googlegroups.com.



--

Daniel LaLiberte

unread,
Jul 6, 2017, 11:45:47 PM7/6/17
to Google Visualization API, charts-announce, Esteban Picone
Thanks Ariel.  Nice clear example!  Here is what I am seeing.

Loading 45.2, I get only two errors both saying: 

?_dc=1499395990479:2 Uncaught TypeError: Ext.Loader.setPath is not a function 
at ?_dc=1499395990479:2

If I add a big timeout around the Ext.onReady() callback function, or rearrange to do the Ext.onReady first, I get more errors:

VM28 extensions::extension:10 Uncaught Natives disabled
Uncaught (in promise) TypeError: l.fireFn.apply is not a function at EXTUTIL.Event.fire (VM123 ext-all-debug.js:329) at Object.onDocumentReady [as onReady] (VM123 ext-all-debug.js:5420) at VM289 app.js:9 at <anonymous>

This suggests to me that there is a problem loading the ExtJS code this way, regardless whether it works or not, and maybe this loading problem was only exposed sufficiently with the new Google Charts loader to cause failures. 

If I load version 44, I still see the same errors as above, but it proceeds to run the XTemplate as desired.  

So it seems that loading is not happening as intended (there should be no errors), but even if things manage to get loaded, they don't behave properly if Google Charts 45.2 is loaded.  

I am suspecting that ExtJS 4.07 (and maybe some other versions from that era) is interfering with the Object and Array prototype methods in a way that is not compatible with more recent code, and the browser native support.

This message looks spot on:
https://www.sencha.com/forum/archive/index.php/t-273538.html
"EDIT : It's a bug. It is caused by ECMAScript 6 support (Array.prototype has function values)

If you call f([1,2,3], obj) in an ECMAScript 5 environment, then the values reference inside the with statement will resolve to obj. However, ECMAScript 6 introduces a values property on Array.prototype (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/prototype) (so that it will be available on every array). So, in a JavaScript environment that supports ECMAScript 6, the values reference inside the with statement will resolve to [1,2,3].values. [...]"

Newer versions of ExtJS have fixed this problem, apparently.  
The new loader does use some ES6 features, in particular, the Promise mechanism.  Moreover, version 45.2 uses some more ES6, and perhaps that is enough to trigger the problems with XTemplate.

So, I don't see a workaround.  I'm not inclined to back out any of the changes I have made in 45.2, and it is difficult to know at this point what changes triggered this old problem in ExtJS 4.07.  You'll probably have to stick with versions 44, 45, or 45.1 (if they still work for you) until you can upgrade your ExtJS.


To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.



--

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--

Ariel Falduto

unread,
Jul 7, 2017, 4:46:32 PM7/7/17
to Google Visualization API, charts-...@google.com, espi...@yahoo.com
Hi Daniel, forget about the ExtJS loader exceptions, they are not related in any way to the issue, they are fiddle related exceptions.
I think a breaking change was introduced in the latest version (45.2). 
I prepared a new js fiddle example with no ExtJS loader code at all, please try it:


Also note above example is failing in chrome but not in firefox or safari.
May be there is a problem with the ES6 transpiler?
Unfortunately I can’t upgrade to a newer version of ExtJS in the short or mid term.
Thanks
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.



--

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.



--

Daniel LaLiberte

unread,
Jul 7, 2017, 7:01:48 PM7/7/17
to Google Visualization API, charts-announce, Esteban Picone
Another very clear example.  Thanks.  I made some elaborations and added comments here:  https://jsfiddle.net/dlaliberte/kw7weduj/7/

I believe the 'breaking' change introduced with 45.2 is merely the use of ES6.  This has the effect of ensuring that the 'values' property is defined on all arrays, as specified here:  
   https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/values
This 'values' property is a function that returns an iterator over the array values.

And when the 'values' property is defined on arrays, then the valid expression: 
  with (someArray) { return values } 
will return that property, which happens to be a function, and hence, length of that function is 0.

So this is actually valid and correct, though bizarre and confusing, and a very good reason to entirely avoid use of JavaScript 'with'.  I believe this also means that Firefox and other browsers are actually wrong, and need to be fixed to behave the same as Chrome.  They should all aim to be consistent in any event.  

This is a problem with ES6, to some extent, because it introduced this new property ('values') on Array prototype, which could affect any program that was trying to use this same property for a different purpose, or doesn't expect it to be there at all.  It is also a problem with JS 'with' because it can result in these kinds of surprises, but that is actually incidental here, and only one of the ways in which this problem can be exposed.

Short of upgrading your ExtJS, maybe there is a patch you could apply to work around the problem, which is in Ext.XTemplate,  tpl.compiled. See http://docs.sencha.com/extjs/4.0.7/source/XTemplate.html  You'll have to replace this function with one that avoids accidental use of this values property.  Or maybe the problem is really in the WITHVALUES definition:

  WITHVALUES = 'with(values){ ',

and every place it is used.  E.g. 

  Ext.functionFactory(VALUES, PARENT, 'try{' + WITHVALUES + RETURN + name + ';}}catch(e){return;}');

Ya, that looks like the problem described in the previous link, better formatted here:  https://www.sencha.com/forum/showthread.php?273538-ExtJS-4-0-7-Chrome-30-0-1599-69-Ext-view-View-fails-to-render-(Ext-XTemplate-fails)

Also note in a later comment: "As far as filing a bug, the code segment you referenced is not in the next version of the code (4.1.0) let alone the current one, and Chrome 30 didn't exist when 4.0.7 released in 2011."

So maybe it will be enough for you to upgrade to ExtJS 4.1.0.


To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.



--

--
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 post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.



--

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--

Oliver G

unread,
Jul 10, 2017, 1:27:33 PM7/10/17
to Google Visualization API, charts-...@google.com, espi...@yahoo.com
Hello,

Apologies  if this has been addressed to-date.

We are having an issue with version 45.2 and multiple charts created using the ChartWrapper class.  In particular, I am finding that when multiple charts are created using the wrapper, only one will render, while the rest will fail with an "Invalid ChartType: " error message.  When I revert back to 45.1, this issue disappears:

Example of failure (two charts, second fails):


Same example with 45.1, success:


Thank you in advance.

Daniel LaLiberte

unread,
Jul 10, 2017, 1:43:38 PM7/10/17
to Google Visualization API, charts-announce, Esteban Picone
Thanks for your report, Oliver.  

That appears to be a legitimate bug, but the use of google.charts.load with no packages is fairly new, so it is not exactly a regression from documented behavior.  If you do include {packages: ['corechart']} in your google.charts.load call, it works fine.

Nevertheless, I will look into it to see if this behavior of dynamically loading all packages can be restored.

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/b11dd281-2e1f-4b3c-bb95-64e516324e38%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Oliver G

unread,
Jul 10, 2017, 2:24:27 PM7/10/17
to Google Visualization API, charts-...@google.com, espi...@yahoo.com
Thank you Daniel,

Your help is very much appreciated; in going with ChartWrapper as a solution for our needs we were following the documentation and examples provided here.
Cheers
Oliver

On Monday, July 10, 2017 at 1:43:38 PM UTC-4, Daniel LaLiberte wrote:
Thanks for your report, Oliver.  

That appears to be a legitimate bug, but the use of google.charts.load with no packages is fairly new, so it is not exactly a regression from documented behavior.  If you do include {packages: ['corechart']} in your google.charts.load call, it works fine.

Nevertheless, I will look into it to see if this behavior of dynamically loading all packages can be restored.
On Mon, Jul 10, 2017 at 1:27 PM, Oliver G <ogjo...@gmail.com> wrote:
Hello,

Apologies  if this has been addressed to-date.

We are having an issue with version 45.2 and multiple charts created using the ChartWrapper class.  In particular, I am finding that when multiple charts are created using the wrapper, only one will render, while the rest will fail with an "Invalid ChartType: " error message.  When I revert back to 45.1, this issue disappears:

Example of failure (two charts, second fails):


Same example with 45.1, success:


Thank you in advance.

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.



--

Daniel LaLiberte

unread,
Jul 10, 2017, 2:27:26 PM7/10/17
to Google Visualization API, charts-announce, Esteban Picone
Ah, so you are right, it is documented.  Well then, I'll fix it pronto.

On Mon, Jul 10, 2017 at 2:24 PM, Oliver G <ogjo...@gmail.com> wrote:
Thank you Daniel,

Your help is very much appreciated; in going with ChartWrapper as a solution for our needs we were following the documentation and examples provided here.
Cheers
Oliver

On Monday, July 10, 2017 at 1:43:38 PM UTC-4, Daniel LaLiberte wrote:
Thanks for your report, Oliver.  

That appears to be a legitimate bug, but the use of google.charts.load with no packages is fairly new, so it is not exactly a regression from documented behavior.  If you do include {packages: ['corechart']} in your google.charts.load call, it works fine.

Nevertheless, I will look into it to see if this behavior of dynamically loading all packages can be restored.
On Mon, Jul 10, 2017 at 1:27 PM, Oliver G <ogjo...@gmail.com> wrote:
Hello,

Apologies  if this has been addressed to-date.

We are having an issue with version 45.2 and multiple charts created using the ChartWrapper class.  In particular, I am finding that when multiple charts are created using the wrapper, only one will render, while the rest will fail with an "Invalid ChartType: " error message.  When I revert back to 45.1, this issue disappears:

Example of failure (two charts, second fails):


Same example with 45.1, success:


Thank you in advance.

--
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 post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.



--

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.

Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/f63a2d22-b305-475c-bb76-5c720b0fb80c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--

Daniel LaLiberte

unread,
Jul 11, 2017, 3:08:09 PM7/11/17
to Google Visualization API, charts-announce, Esteban Picone
Hi Oliver,

This problem that you discovered should now be fixed.  It is again possible to initially load no packages, and then load the same package multiple times, in particular via the ChartWrapper.  


--

Oliver G

unread,
Jul 11, 2017, 5:04:55 PM7/11/17
to Google Visualization API, charts-...@google.com, espi...@yahoo.com
Daniel,

Thank you for the quick turn-around.  Things look good on my end.

Oliver
Thank you Daniel,
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.



--

--
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+unsub...@googlegroups.com.

To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.



--

Oliver G

unread,
Jul 27, 2017, 1:21:17 PM7/27/17
to Google Visualization API, charts-...@google.com
Daniel, we are encountering a new problem with 45.2 + ChartWrapper (it may not be specific to ChartWrapper, however this is where its manifesting).  This issue does not show up in 45.1.

Description:
It has to do with the functionality embodied in the "explorer"/zoom option-set.  In particular when a chart is freshly created everything (zoom functionality) works fine.  However, once the chart data is updated via wrapper.setDataTable/wrapper.draw, the zoom functionality does not convey.  


To reproduce: 
Step 1: Use the drag-to-zoom to sub-select the original chart (everything works fine).
Step 2. Click "Update chart data" (chart updates as expected).
Step 3. Use the drag-to-zoom to sub-select the updated chart (no response).

Thank you in advance.


On Thursday, June 15, 2017 at 3:09:38 PM UTC-4, Daniel LaLiberte wrote:

You can now load Google Charts version '45.2' by loading 'upcoming'.  Please test this version and let us know if you experience any new problems.


At this time, 'current' is still '45.1'.  You can continue to load version '45' or '45.1' by specifying one of those versions.

Anticipated production release date: June 28

  On this date, loading 'current' or 'upcoming' will load '45.2'. 

This version includes a few bug fixes and many changes that involve internal refactoring, particularly in how options are processed, but there should be no visible changes.


Summary of changes for v45.2:


  • Corecharts

    • Added tooltip.boxStyle options: e.g.

 'tooltip': {

   'boxStyle': {

       'stroke': '#b2b2b2',  'strokeOpacity': 1,  'strokeWidth': 1.5,

       'fill': 'white',  'fillOpacity': 1,

       'shadow': {  'radius': 1, 'opacity': 0.2,  'xOffset': 0,  'yOffset': 2 }

   }}

    • Fix AreaChart legend items to use areaOpacity option.

    • Fix infinite loop when formatted domain values are (incorrectly) numeric.

  • Table

    • Fix paging buttons.

    • Add column type to header cell classlist.

    • Respect column property.

    • Fix accessibility labels when sorting is enabled.

  • Gantt

    • Fix selection object to include row index.


Daniel LaLiberte

unread,
Jul 27, 2017, 2:20:24 PM7/27/17
to Google Visualization API, charts-announce
Oliver,

Thanks for the demo of this problem.  I see it happening as well, and it does appear to be a bug.  No idea why it is happening or how you can work around it without recreating the ChartWrapper (or chart). 

Setting the options again in your changeChart function doesn't help.  It doesn't seem to help to have an explicit viewWindow for the vAxis.

Also, if you don't drag to zoom before clicking "update chart data", then the zoom does work in the new chart.  So it is the first usage that seems to corrupt subsequent usages after a redraw.  

It is not related to the ChartWrapper since it happens with a ColumnChart by itself.

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.

Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/aae0b389-a010-4332-b39c-91fe0cf04202%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--

Daniel LaLiberte

unread,
Jul 27, 2017, 5:05:36 PM7/27/17
to Google Visualization API, charts-announce
Oliver,

If figured out the problem, and I have a fix.  The bad news is that no workaround is possible other than recreating the chart or chartwrapper.

To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.
--

Oliver G

unread,
Jul 27, 2017, 5:34:02 PM7/27/17
to Google Visualization API, charts-...@google.com
Daniel - thanks for being so quick.

I am also encountering the same problem with only calling `setOption(s)` (without updating the data-set).  Is destroying/re-instantiating/re-drawing as a solution fairly expensive relative to the status quo (assuming that updating options currently doesn't re-render the entire chart)?

Thanks again
O
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.



--

Daniel LaLiberte

unread,
Jul 27, 2017, 6:11:34 PM7/27/17
to Google Visualization API, charts-announce
When you redraw the same chart, it does try to reduce some of the recalculations, but we bail out pretty quickly for most changes, so there is not usually much benefit.   Go ahead and regenerate the chart and see how it goes.

To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
--



--

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.

Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/ca41c85f-e47d-4fe0-b300-f474dfb9927f%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--

Oliver G

unread,
Jul 28, 2017, 7:58:43 AM7/28/17
to Google Visualization API, charts-...@google.com
Thanks Daniel.

You are right - I suspect it will make very little difference in the jsfiddle example regardless of what happens on the back end.

We have a pretty varied use case for the API, across many of the charts and often with thousands of rows in the underlying data-set.  In time we may move to just re-generating the charts as you suggest, but until such time that we can assess the impact and get a sense of the scope of changes required on our end I think we'll just downgrade to 45.1.

Thanks again for your help.
Oliver
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
--



--

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.



--

Chucky Ellison

unread,
Aug 16, 2017, 6:33:55 PM8/16/17
to Google Visualization API, charts-...@google.com
I'm also running into this problem (can't pan/zoom after updating the chart) on my site.  It's good to hear that there's a fix though!  When will the fix be deployed?

Thanks!
-Chucky
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.



--
Reply all
Reply to author
Forward
0 new messages