Google Charts 'upcoming' release of v46 again

1,333 views
Skip to first unread message

Daniel LaLiberte

unread,
Sep 17, 2018, 5:31:53 PM9/17/18
to Google Visualization API, charts-announce
I've updated the 'upcoming' v46 release again.   You can now load Google Charts version '46' by loading 'upcoming'.  Please test this version and let us know if you experience any new problems.  


At this time, 'current' is still '45.2'.  You can continue to load version '45.2' by specifying that version.

Anticipated production release date: Oct 1
  On this date, loading 'current' or 'upcoming' will load '46'. 

In addition to the changes previously announced in https://groups.google.com/d/msg/google-visualization-api/yREgaC4x0oU/eHoBqHUNCQAJ, several more changes have been made, mostly fixes to previous changes.  The following list merges all the changes here, and highlights the new changes.

  • Corecharts
  • All gridline and tick generation now computes the number of gridlines based on other options (see below).  If you specify a number for gridlines.count, it will only be used as an approximation. 
  • Minor gridlines are even more dynamic since the appropriate number of minor gridlines depends on the interval between the major gridlines.  The default for numeric axes is no minor gridlines, but for dates and times, minor gridlines may be shown if they fit. Specify '{ minorGridlines: { count: 0 }}' to force no minor gridlines, or '{ minorGridlines: { count: 1 }}' to enable minor gridlines if they fit.
  • New 'gridlines.minSpacing' option lets you specify the minimum screen space between major gridlines in pixels.  Default is 40 for linear scales, 20 for log scales. 
  • New 'gridlines.interval' option lets you specify an array of sizes of the gridlines as data values. The default for linear scales is { interval: [1, 2, 2.5, 5] } means the gridline values can fall on every unit (1), on even units (2), or on multiples of 2.5 or 5.  Any power of 10 of these values are also considered.   For log scales, the default is [1, 2, 5]. This option is only for numeric axes at this time, and it is analogous to the 'gridlines.units.<unit>.interval' options which is used only for dates and times.
  • Add options for gridlines.multiple and minorGridlines.multiple, such that gridline and ticks values must be a multiple of this option's value.  E.g. To force ticks to be integers, specify gridlines.multiple = 1.
  • Gridlines will usually be rejected if formatted tick labels for numbers are duplicated, so you can specify 'format:"#"' to only show integer ticks without risking generation of duplicate ticks.  But if all alternatives fail, the best case will still be used.  
  • New 'viewWindow.maxPadding' lets you specify the maximum screen space before or after the data range, in percentage of the data range (as a string, e.g. '50%') or number of pixels.  The default is 30%.  Note that the data might extend beyond the first or last gridline occasionally, if it is not too much. 
  • Many changes to the log scale and mirror log scale are included in this release.
  • Several changes were made to the axis tick and gridline generation to allow tighter packing of ticks that don't overlap.
    • Allow negative slanted angle, to slant the 'other' way.  
    • Disable skipping and alternating (i.e. multiple staggered lines) for dates and times, by default.
  • Expand viewWindow to include explicit ticks, if outside the data range.  Explicit viewWindow min or max options can override.  This is a change to the previous behavior which acted more like 'maximized' mode with explicit ticks.
  • Fix for explorer mode, which was disabled after the first redraw.
  • Fixed ChartWrapper refreshInterval to actually refresh.
  • Trendline equations now use column labels instead of just 'x' and 'y'.
  • Fix polynomial trendlines to fail silently if there is no data.
  • Add option to specify legend default page index (legend.pageIndex). 
  • Add event (legendpagination) to receive updates of legend pagination changes; data given to event handler is         'currentPageIndex' and 'totalPages'.
  • Number format for 'short' and 'long' patterns now use 3 significant digits.
  • The timeofday formatting is fixed to use 24 hour (HH) values for the hours by default instead of 12 hour (hh) values. 
  • Explicit formats for dates and times will now override 'unit' formats.
  • ColumnChart and BarChart
    • Fixed detection of minimum bar size (the difference between adjacent values) to work with dates and times.
  • Table
    • Support 'className' property for rows.
    • Add user specified column and cell className properties to default properties (rather than replace them), similar to row properties.
  • Data
    • Fix the data.group function to allow multiple aggregations to use the same column.
  • Content Security Policy (CSP) compliance
    • Remove uses of eval for JSON deserialization.

--

Daniel LaLiberte

unread,
Oct 1, 2018, 7:21:04 PM10/1/18
to Google Visualization API, charts-announce
As of Oct 1, v46 is now 'current', and 'upcoming' will continue to load v46 until we start the next release cycle.

If you are experiencing new problems with v46, please post in the google-visualization-api group, or on the issues list at https://github.com/google/google-visualization-issues/issues .  Alternatively, you can switch to using the previous release by changing 'current' to '45.2', which will remain available indefinitely.  


Daniel LaLiberte

unread,
Oct 11, 2018, 4:57:27 PM10/11/18
to Google Visualization API, charts-announce
I've updated v46 with several fixes, mostly for the date-time ticks and gridlines:
  • Support i18n and localization for date-time unit format options.
  • Fix for missing minor gridline formats, which results in no ticks at all.
  • Increase min spacing of minor gridlines for date-time axes, and decrease min spacing for notches.
  • Disable slanting and alternation by default for dates and times.
  • Fix for line breaking that would sometimes drop the last line.
  • Fix for histogram with only one bucket.
  • Fix textPosition == 'none', to generate gridlines with no ticks.

Greg Slocum

unread,
Nov 6, 2018, 7:43:52 PM11/6/18
to Google Visualization API
I have what seems a simple problem, but can't find the right answer.

I have a table with 17 rows. I want to format the eighth, fifteenth and seventeenth rows bold.
PositionA.htm

Daniel LaLiberte

unread,
Nov 15, 2018, 6:24:52 AM11/15/18
to [email protected], [email protected]
I am updating v46 yet again with a few more fixes based on reports from the last release.   Hopefully, this will be the last update of v46, but please let us know if you have problems.

This update (46.2) will be available as 'upcoming' for a couple days, and then I will switch '46', '46.1' and 'current' to load the same.
  • Fix Histogram domain axis formatting to use format option.
  • Fix slow rendering of discrete axis ticks with a large number of string values.  (I suspect the slower rendering was exposed by the earlier fix for line breaking.)
  • Expand number axes minimally to nearest major gridline, for 'pretty' mode.  Date and time gridlines expand to nearest major or minor gridlines.
    • This also obsoletes the recently added maxPadding option since the whole point was to find the nearest gridline within the padding distance. 
  • Fix several potential XSS vulnerabilities.
  • Fix ticks to be more backward compatible. 
    • Compute minSpacing from count, if user specifies count and not minSpacing. 
    • Compute count from minSpacing, if user specifies minSpacing and not count. 
    • Set minorGridlines color to none if major gridlines color is none.
  • Crank number precision back up to the max, wherever it seems safe.

Chris Dubé

unread,
Nov 29, 2018, 1:57:44 PM11/29/18
to Google Visualization API
Hi,

I guess that 46.2 become 'current' some time in the last few days.  I have a set of line charts with log vertical axes, which no longer show minor gridlines.  I cannot work out how to get the minor gridlines to show with the 'current' release (and whatever was current up until a few days ago does not seem to be available any more through a frozen release).  Also there is a new vAxis baseline shown with the data value 0E0 which is not correct - on a log axis there is no 0E0 value.  Fortunately a colleague emailed a screenshot of one of the charts (and added a couple of minor annotations) so I have attached images of before and after.

For the gridlines I have tried:
vAxis.minorGridlines.count (has no effect whatever count value I use)
vAxis.gridlines.minSpacing
chartArea.height increase
increasing the height of the container div HTML tag

None of these cause the minor gridlines to appear.

I particularly want the minor gridlines on the vertical axis because they give a clear visual reminder that the scale is logarithmic.

Attached are the before and after screenshots, and the HTML source.

Can you help please?

Thanks
Chris
before.png
after.png
fer-plot.html

Daniel LaLiberte

unread,
Nov 29, 2018, 6:49:24 PM11/29/18
to [email protected]
Yes, Chris, the update to v46.2 happened a couple days ago, a week or two later than I had hoped.  This version replaced v46.1 (which previously replaced v46), so they are all the same v46.  Generally bugs are fixed, but apparently a few new ones were created, though they are rare and unusual cases (mostly involving no data, or only one data point).  You can try '45.2', though it may have different problems.

In your situation, the problem appears to be the combination of tiny values with a large range (many orders of magnitude).  I'm not sure yet, but the missing minor gridlines might be due to a rounding error.   I don't have a workaround for you, other than using previous versions.

The 0E0 tick value on the log scale might also be due to a rounding error.  You can avoid having the 0 show up at all by adding a viewWindow.min of 1E-7, but that could be a problem if your actual min varies.  

Hope that helps.

--
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 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/74fe37d3-f74b-4cc0-9aac-83d65a31e96d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Chris Dubé

unread,
Nov 29, 2018, 6:55:56 PM11/29/18
to Google Visualization API
Hi Daniel,

Thanks for your quick reply.

Is it possible to make v46.1 available as a frozen version so that I can use that?

Thanks
Chris

Daniel LaLiberte

unread,
Nov 29, 2018, 7:40:58 PM11/29/18
to [email protected]
Yes, it would be possible to make 46.1 available.  I merely have to change the loader configuration.  

But I no longer have separate release notes, and there are other serious bugs in 46.1 that I don't want to expose people to now that they are fixed in 46.2.  So I would much rather bury 46.1.  I'll think about it, but I'll probably leave it as is, unless I hear about more serious 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 [email protected].
To post to this group, send email to [email protected].
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/2d1b0087-c010-45fe-87c2-471d7fc234f8%40googlegroups.com.

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

Chris Dubé

unread,
Nov 30, 2018, 6:15:52 PM11/30/18
to Google Visualization API
Hi Daniel,

I've used version 45.2 and with appropriate options that is working fine for me.  So I don't need version 46.1, thanks.

Thanks
Chris

Sandeep Bains

unread,
Dec 20, 2018, 11:05:18 PM12/20/18
to Google Visualization API
The Dashboard search "string filter" hangs the page if in case there is no match. It works perfectly fine with version 45.2 but broken with 46/current...
Reply all
Reply to author
Forward
0 new messages