OK, I can agree that it works differently than the previous version. However, I believe this new interpretation of the options makes more sense.
Here is a variation of your jsfiddle that shows more rows than will fit in the container, thus freezing the header, but without specifying the height in the chart options: https://jsfiddle.net/dlaliberte/5ed4oeLe/1/ If you have fewer rows than needed to fill the page, then there is nothing to scroll anyway. Will this work for your application? On Mon, Aug 24, 2015 at 4:58 PM, Paul Benson <[email protected]> wrote: > Hello Daniel, I created an example on jfiddle, > > https://jsfiddle.net/5ed4oeLe/. > > As you can see, this will make rows taller so it fits in the size of > the chart. This didn't happen with the previous version, so it was > easier to freeze the header and account for changes in size of data > set returned. > > On Mon, Aug 24, 2015 at 3:52 PM, 'Daniel LaLiberte' via Google > Visualization API <[email protected]> wrote: > > Hi Paul, > > > > You should be able to freeze the header row with heights other than 100%. > > And you can also specify a height on the container. > > > > If you are still having trouble figuring out how to make it work, can you > > point me at your page, or set up an example on jsfiddle? Thanks. > > > > > > On Mon, Aug 24, 2015 at 4:42 PM, Paul Benson <[email protected]> > wrote: > >> > >> I have noticed with the new release that when I specify a height of the > >> table chart (required to freeze header row), the rows will resize to > fit the > >> total height of the specified chart height. So If I have only 2 rows > >> returned they are greatly impacted by resize. > >> > >> > >> On Thursday, April 30, 2015 at 1:32:05 PM UTC-5, Daniel LaLiberte wrote: > >>> > >>> We have pushed an update of the new Google Charts Release Candidate > (RC) > >>> - V42. This should start to be available within a couple hours. > >>> > >>> This update fixes a couple bugs and adds a couple small features: > >>> > >>> The 100% stacking feature for AreaChart shows correct values in > tooltips. > >>> Material charts focus and selection events fixed. > >>> Material charts sizing issues fixed. > >>> ScatterChart now works with discrete domain axis and supports > >>> annotations. > >>> Default trendline options can be specified at the top level within the > >>> 'trendlines' option. > >>> PieChart now supports custom tooltips. > >>> > >>> > >>> Candidate release date: April 30, 2015 > >>> > >>> > >>> Anticipated production release date: as soon as May 11, but not before > a > >>> frozen V41 is available. This date represents a delay by one week from > the > >>> previous announcement. > >>> > >>> > >>> Please test this candidate release by changing your google.load() calls > >>> to load "1.1" instead of "1" or "1.0". If this works for you, great. > If > >>> you find problems, please report your issues in this forum: > >>> [email protected]. > >>> > >>> Sometime before the production release, we will make available to you a > >>> way for you to switch from loading the production version (which you > get > >>> when you load "1" or "1.0") to be able to load a frozen version of > V41. So > >>> if V42 doesn't work for you, and we can't resolve the issues in time, > you > >>> will be able to continue using V41. > >>> > >>> Summary of changes for v42: > >>> > >>> Corecharts: > >>> > >>> ColumnChart, BarChart, AreaChart, and SteppedAreaChart now support > >>> isStacked: ‘percent’ (for scaling to 100% of data for each category) > and > >>> isStacked: ‘relative’ (for scaling to the range 0..1) > >>> > >>> For all corecharts, the default baseline for axes will no longer be at > >>> the edge of the chart. The default baseline value of 0 will be used > for > >>> numeric axes, but for backward compatibility with existing charts, it > won’t > >>> automatically be included in the chart unless it is “close enough” to > the > >>> data. You can force inclusion of the baseline just by adding > baseline: 0 to > >>> your options. For date and datetime axes, there is no default > baseline, but > >>> you can specify one if you would like. > >>> > >>> Corechart legends use line, area, and point style corresponding to each > >>> series. > >>> > >>> All text options for corecharts now support opacity. > >>> > >>> The webfont loader will be used to load unknown fonts, which could > cause > >>> your chart drawing to be delayed. Font names are case-insensitive. > >>> > >>> Startup animation now works with DataViews, and when combined with the > >>> async drawing mode. > >>> > >>> Fix clearChart, when used before the chart was first drawn. > >>> > >>> ‘pointsVisible’ option for top-level, series, and trendlines. This > option > >>> controls whether points should be visible by default. This allows you > to > >>> change the pointSize while keeping the points hidden. > >>> > >>> HTML tooltip position is fixed. > >>> > >>> ScatterChart now works with discrete domain axis and supports > >>> annotations. > >>> > >>> PieChart now supports custom tooltips. > >>> > >>> Sankey: > >>> > >>> You can now select nodes. This can be enabled via > >>> ‘sankey.node.interactivity’: true > >>> > >>> Adding the ability to specify Sankey interactivity via the chart > options. > >>> Options are generally specified under the style of whatever is being > >>> specified, by adding an object with modified style attributes at one > of the > >>> following keys: 'selected', 'focused', 'unselected', 'unfocused'. > >>> > >>> Colors > >>> > >>> Sankey now supports the ‘style’ role > >>> > >>> Nodes can now be colored uniquely by setting the option > >>> ‘sankey.node.colorMode’: ‘unique’ > >>> > >>> Links can now be colored. The coloring mode can be changed by the > option > >>> ‘sankey.link.colorMode’. Valid values are: > >>> > >>> ‘unique’—each link gets its own color. > >>> > >>> ‘source’—each link uses the color of its source node. > >>> > >>> ‘target’—each link uses the color of its target node. > >>> > >>> ‘gradient’—each link is colored by a gradient that goes from the color > of > >>> its source node to the color of its target node. > >>> > >>> NOTE: If node coloring is set to the default or the palettes for nodes > >>> and links are different, ‘source’, ‘target’, and ‘gradient’ will use > the > >>> colors that would be assigned to the nodes if the colorMode was > ‘unique’ and > >>> links and nodes shared a palette. > >>> > >>> The color palette for the nodes may now be changed via > >>> ‘sankey.node.colors’ > >>> > >>> The color palette for the links may now be changed via > >>> ‘sankey.link.colors’ > >>> > >>> Default tooltips (both HTML and SVG) can now be generated by links and > >>> custom tooltips are supported via the ‘tooltip’ role > >>> > >>> Timeline: > >>> > >>> SVG tooltips are now supported. > >>> > >>> Custom tooltips now supported. > >>> > >>> colors will cycle if more are required than available. > >>> > >>> Calendar > >>> > >>> SVG tooltips are now supported. > >>> > >>> Custom tooltips now supported. > >>> > >>> Trendlines - pointsVisible option. > >>> > >>> Table chart > >>> > >>> “width” and “height” options may either be unspecified, meaning the > table > >>> should shrink as much as possible, or ‘100%’, meaning the table should > >>> expand as much as possible. > >>> > >>> Removed duplicate table used for frozen table header. > >>> > >>> Frozen columns, useful when you have more columns than will fit within > >>> available width. E.g. the leftmost 2 columns may be frozen with > >>> “frozenColumns”: 2. > >>> > >>> Specify the number of paging buttons with the “pagingButtons”: # > option. > >>> The number of rows per page will be based on that, unless you also > specify > >>> the “pageSize” option. > >>> > >>> “rtlTable” now works with paging or scrolling, but not (yet) with > >>> frozenColumns. > >>> > >>> Renamed some css classes (e.g. ‘content’) to avoid conflicts. > >>> > >>> Column headers now do not wrap by default. > >>> > >>> Material charts (Bar, Line, and Scatter, so far): > >>> > >>> Better support for date, datetime, and timeofday axes. > >>> > >>> Fix sizing problems with multiple charts on the same page. > >>> > >>> May now be used with ChartWrapper. > >>> > >>> AnnotationChart: > >>> > >>> Fixes for selecting annotations and color of range selector. > >>> > >>> Allow AnnotationChart to specify order of annotations table, using > >>> table.sortAscending option. > >>> > >>> Map > >>> > >>> A set of coordinates is no longer ignored if its latitude/longitude > >>> values are 0 > >>> > >>> > >>> > >>> > >>> > >>> -- > >>> Daniel LaLiberte - 978-394-1058 > >>> [email protected] 5CC, Cambridge MA > >>> [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/92bc9854-626f-4d91-a597-6a60988009aa%40googlegroups.com > . > >> > >> For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > -- > > Daniel LaLiberte - 978-394-1058 > > [email protected] 5CC, Cambridge MA > > [email protected] 9 Juniper Ridge Road, Acton MA > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "Google Visualization API" group. > > To unsubscribe from this topic, visit > > > https://groups.google.com/d/topic/google-visualization-api/XxP1zYbWQRE/unsubscribe > . > > To unsubscribe from this group and all its topics, 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/CAOtcSJM0hS21mDDOCDd95RaWTF6bBMxad1WwLmQ-k3XK1cN9mQ%40mail.gmail.com > . > > > > For more options, visit https://groups.google.com/d/optout. > > -- > 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/CAPb%3D3OmBieG1jMiojgY%3DLb6V-LvSJLsx75bJdP4sVv15xgXF0g%40mail.gmail.com > . > 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/CAOtcSJM%2BqQAN7uS%2BSsqgYxJrxj0xrAmpdpWigGqMBLoL909iHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
