Lewis, the table elements have changed, so if you have css code that
depends on internal use of css, then you will have to update accordingly,
or better, use the cssClassNames option so your own class names will be
used.
The width of the table content being set to 0 is most likely due to drawing
the Table chart in a container that is not visible at the time you call
draw(). You can probably work around this by including { width: '100%' }
in your options, or some other pixel value. I'm not sure yet whether we
will have another change for table charts that would default the width to
100%.
If you can provide a link to your page that shows the behavior you are
seeing, or reproduce it in jsfiddle, we will be able to check it out and
have a better chance of resolving this sooner. Thanks.
On Fri, Feb 20, 2015 at 9:04 AM, Daniel LaLiberte <[email protected]>
wrote:
> James, the fixes did go out, one of which addressed the indexing of
> selections in Dashboards.
>
> We have been updating the documentation, but there is always more to do.
>
> We are glad you are getting value from Google Charts. Sorry for the
> inconveniences this release has caused. Hopefully they will all be
> resolved shortly.
>
> On Fri, Feb 20, 2015 at 8:53 AM, James Tanner <[email protected]>
> wrote:
>
>> Right on. The onfocus error is the one I surmised was due to your adding
>> proper headings to the tables (which incidentally, a huge chunk of my code
>> is for making the tables more accessible, so I applaud the change). I
>> appreciate the confirmation and the suggestion for a fix.
>>
>> However, I'm not seeing the second error in dev tools. Has that fix been
>> processed?
>>
>> Final question: do you know when the API documentation will be updated
>> for the changes?
>>
>> Thanks for everything Daniel. Y'all are doing great work.
>>
>> On Thursday, February 19, 2015 at 12:28:16 PM UTC-6, Daniel LaLiberte
>> wrote:
>>>
>>> James,
>>>
>>> I'm seeing two types of errors in the developer tools on your page now:
>>>
>>> Uncaught TypeError: Cannot set property 'onfocus' of undefined
>>> Uncaught Error: Invalid row index 5122. Should be in the range [0-70].
>>>
>>> The second error, we have a fix for.
>>>
>>> The 'onfocus' error seems to be due to this query resulting in an empty
>>> array, so your attempt to set the onfocus property of the first element
>>> fails.:
>>>
>>> var list2 = document.querySelectorAll('td.
>>> google-visualization-table-th')
>>>
>>> The way we set the classes on the table elements has changed, so this
>>> querySelector will fail. To be more reliable, and allow us to change how
>>> the table elements are laid out, you should instead use the cssClassNames
>>> option to specify classes that will be added to elements.
>>>
>>>
>>>
>>> On Thu, Feb 19, 2015 at 1:02 PM, James Tanner <[email protected]>
>>> wrote:
>>>
>>> Near as I can tell, the problem isn't that the table is being drawn with
>>> a width of 0, the problem is that the table is not being drawn at all. The
>>> browser is seeing an empty div where the table used to be.
>>>
>>> Here's how the table is designed to populate. It's admittedly a bit more
>>> complex than most:
>>>
>>> - I'm actually using two datasets here. The main dataset is the
>>> subject of the visible controls; these controls are constantly in a state
>>> where they're collectively selecting one (and only one) row of the
>>> dataset.
>>> - The data being shown in the pie, bar, and large table come from
>>> that selected row.
>>> - I have another control which is not drawn on the page (it's
>>> assigned to a div with a matching ID but also the property
>>> "display:none")
>>> that selects the unique ID column [0] in the main dataset. It's a unique
>>> ID
>>> so there should only be one available, corresponding to the selected row.
>>> - The missing table is connected to that invisible control
>>> (tabPicker) via this function, triggered when the bar chart (bChart) is
>>> ready:
>>> -
>>> - google.visualization.events.addListener(bChart, 'ready',
>>> function () {
>>> - var uniqueID = tabPicker.getState().selectedValues[0];
>>> - var rows = sumdata.getFilteredRows([{column: 0, value:
>>> uniqueID}]);
>>> - var view = new google.visualization.DataView(sumdata);
>>> - view.setRows(rows);
>>> - sumTable.setDataTable(view);
>>> - sumTable.draw();
>>> - });
>>> - For each unique ID there should be five rows in the second
>>> dataset, and it should display those rows in a table above the pie chart.
>>> It summarizes the selections made in the controls so that the results can
>>> be comfortably printed on one page.
>>>
>>> Thank you for notice about the rollback. I'm presuming that these
>>> changes will be coming out eventually though, so if you have any insight as
>>> to why the above process isn't working with V41 I'd love to hear it. Also,
>>> any tips/links about working with beta would be nice.
>>>
>>> Thanks again!
>>>
>>>
>>> On Thursday, February 19, 2015 at 10:29:16 AM UTC-6, Daniel LaLiberte
>>> wrote:
>>>
>>> James, do you know if you are drawing the table when the container is
>>> not visible, if it has width 0? That could be the cause of the table
>>> ending up width 0.
>>>
>>> On Thu, Feb 19, 2015 at 11:02 AM, James Tanner <[email protected]>
>>> wrote:
>>>
>>> Is the list of changes that rolled out this morning complete? Several of
>>> our dashboards and reports use Google Charts and this morning they’re all
>>> broken, and the changes listed below don’t explain all the errors I’m
>>> seeing.
>>>
>>> Here’s one example of a broken page: http://www.lmci.state.t
>>> x.us/researchers/dashboard/Workforce/Workforce_2011_12/wfdash1112.asp.
>>> There’s one table that won’t draw for reasons I cannot fathom – no error
>>> messages are being generated anywhere, no changes in the candidate summary
>>> sound relevant to how the table is created – and another table generating
>>> an error that I originally believed happened because you’ve changed the
>>> table formatting to include TH and THEAD, but won’t behave correctly when I
>>> make the obvious changes to address that problem so maybe that’s not the
>>> only issue:
>>>
>>> I'm supposed to be presenting these pages to a large conference in two
>>> weeks so any help I can get would be appreciated. If the candidate gets
>>> rolled back I'd also like to know how to work with these pages in beta so
>>> we don't get trapdoored the day of the conference. Thank you!
>>>
>>> James
>>>
>>>
>>> On Tuesday, January 13, 2015 at 9:35:21 AM UTC-6, Daniel LaLiberte wrote:
>>>
>>> We have pushed a new Google Charts Release Candidate (RC) - V41
>>>
>>> Candidate release date: January 13, 2015
>>>
>>>
>>> Anticipated production release date: January 27, 2015
>>>
>>>
>>> New features / bugs fixed:
>>>
>>>
>>>
>>> -
>>>
>>> Calendar chart - support 0 values.
>>> -
>>>
>>> Histogram - automatically constrain number of buckets to avoid being
>>> too small.
>>> -
>>>
>>> Material charts
>>> -
>>>
>>> Add ability to customize series colors via the colors option.
>>> -
>>>
>>> Add line chart
>>> -
>>>
>>> Add scatter chart
>>> -
>>>
>>> Subtitle is now supported when using convertOptions()
>>> -
>>>
>>> Map Visualization
>>> -
>>>
>>> Zoom level fix - see https://code.google.com/p/goog
>>> le-visualization-api-issues/issues/detail?id=747
>>>
>>> <https://code.google.com/p/google-visualization-api-issues/issues/detail?id=747>
>>> -
>>>
>>> Support ‘styled’ maps.
>>> -
>>>
>>> Support multiple types of custom markers.
>>> -
>>>
>>> Candlestick chart - now works with vertical orientation.
>>> -
>>>
>>> Corecharts
>>> -
>>>
>>> Startup animation for most corecharts - add startup:true to
>>> ‘animation’ option.
>>> -
>>>
>>> Add clearChart() to several charts that were missing this
>>> function.
>>> -
>>>
>>> Vertical axis ticks positioned inside the chart area can now use
>>> entire chartArea.width.
>>> -
>>>
>>> Handle null values more consistently, especially for JSON
>>> formatted tables.
>>> -
>>>
>>> Add ‘allowAsync’ option to draw asynchronously.
>>> -
>>>
>>> Allow timeofday values to have 1 to 7 elements.
>>> -
>>>
>>> Columns may be referenced by id or label, in addition to index
>>> number.
>>> -
>>>
>>> Generalize ‘style’ role.
>>> -
>>>
>>> Tooltip support for RTL.
>>> -
>>>
>>> Material lite theme added (add theme: ‘material’ option)
>>> -
>>>
>>> HTML tooltips
>>> -
>>>
>>> Fix the positioning of the HTML tooltips such that they’re
>>> relative to the container
>>> -
>>>
>>> Fix “tooltip tag is ‘undefined’” bug
>>> -
>>>
>>> Use color property of text style
>>> -
>>>
>>> Trendlines
>>> -
>>>
>>> Fix for log scale
>>> -
>>>
>>> Allow tooltips to be disabled per trendline
>>> -
>>>
>>> Work with multiple vertical axes.
>>> -
>>>
>>> Work with animation
>>> -
>>>
>>> Annotations - avoid covering annotation with annotation tooltip.
>>> -
>>>
>>> Table chart
>>> -
>>>
>>> Remove prior selection when draw() is called.
>>> -
>>>
>>> Use THEAD and TH elements for table header.
>>> -
>>>
>>> Preserve header between draw() calls to work with accessibility
>>> tools.
>>> -
>>>
>>> AnnotationChart
>>> -
>>>
>>> Reverse order of annotations in table.
>>> -
>>>
>>> Preserve series colors when hiding and showing series.
>>> -
>>>
>>> Restore width and height to default when not specified.
>>> -
>>>
>>> Set chart view window based on the range selector position.
>>> -
>>>
>>> Gauge chart - fix shrinking on subsequent draw() calls.
>>> -
>>>
>>> Dashboards - add getSelection() method that returns a union of all
>>> selections in the dashboard.
>>> -
>>>
>>> ChartWrapper and ControlWrapper parameters now allow ‘container’
>>> element, as alternative to ‘containerId’.
>>> -
>>>
>>> Performance improvements for ChartRangeFilter, and for charts that
>>> use category focus tooltips.
>>> -
>>>
>>> Chart editor
>>> -
>>>
>>> Hide things that are not relevant (e.g. the legend menu when
>>> there are no legend items)
>>> -
>>>
>>> Hide histogram bucket item dividers (by default)
>>> -
>>>
>>> Piechart color fixes
>>> -
>>>
>>> Themes support
>>> -
>>>
>>> Polynomial trendline support
>>> -
>>>
>>> Enable trendlines for date-based axes, and for area charts
>>> -
>>>
>>> Click editor support for min/max values.
>>> -
>>>
>>> Bar chart support for continuous axes and trendlines.
>>>
>>>
>>>
>>> Please test your product is functioning correctly with the new release
>>> candidate and report any issue you encounter to
>>> [email protected].
>>>
>>>
>>> --
>>> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
>>> - 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>>
>>> --
>>> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
>>> - 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>>
>>> --
>>> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
>>> - 978-394-1058
>>> [email protected] 5CC, Cambridge MA
>>> daniel.l...@GMai
>>> ...
>>
>> --
>> 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.
>> 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
>
--
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.
For more options, visit https://groups.google.com/d/optout.
