Good to know. It still seems kind of weird that when I create the Table in a ChartWrapper (as part of a Dashboard) and load the 'controls' package by itself, the problem manifests, but if I load the 'table' package alongside 'controls', it works fine.
On Sunday, April 29, 2012 4:36:43 AM UTC-4, h wrote: > > Hey > > Sorry for the late response. > > It seems that the normalize.css file is setting > *border-collapse: collapse;* > > If you remove this rule the table renders fine. > I guess the table chart should handle external css though adapting to any > random css is a challenging task. > For now it seems like a simple fix on your end to override this property > for the chart <div>. > > > HTH > ChartMan > > > On Wed, Apr 25, 2012 at 10:51 PM, asgallant <[email protected]>wrote: > >> It is worth noting that this only occurs when loading the 'controls' >> package and creating a ChartWrapper for the Table. If I load the 'table' >> package, the problem goes away. >> >> On Wednesday, April 25, 2012 3:33:30 PM UTC-4, asgallant wrote: >>> >>> I just built a new Table using the fixed header capabilities of the >>> Table visualizations, and I noticed what might be a bug: the second >>> rendered table (used to create the fixed header) gets assigned the wrong >>> height in Chrome, IE, Opera, and Safari (in IE, it gets height: 0, in the >>> others it is too short by varying amounts from run to run) instead of the >>> height of the header row, as it should be getting. The IE header problem >>> seems to be independent of anything I do, see: http://jsfiddle.net/** >>> 6yuFb/ <http://jsfiddle.net/6yuFb/> >>> >>> What's weird about it is that in non-IE browsers, *sometimes* the >>> height is correct, and if I draw the table with nothing else on the page, >>> it seems to be always correct. I went searching for CSS/javascript on my >>> end that could be causing the problem, and identified a CSS file that, when >>> removed, seems to allow the Tables to draw properly (nothing else has any >>> impact). The problem with this is that there is nothing in that CSS that >>> has anything to do with the table (and it's contents are critical for the >>> rest of the page to display correctly). Furthermore, the height is a >>> property set by the API, not assigned by CSS, so the CSS file shouldn't be >>> a factor. >>> >>> I haven't yet been able to replicate the problem outside my development >>> environment, which isn't very helpful to you guys. I'd share a link to the >>> page, but the server is restricted by IP. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Visualization API" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/google-visualization-api/-/JZyI1qDMHaUJ. >> >> To post to this group, send email to >> [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/google-visualization-api?hl=en. >> > > -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/4nk_TN3QWkwJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
