Hi Daniel, It looks like whatever change was pushed in the last 12 hrs broke our tables again. We are now seeing the headers misaligned and tables not filling the full width of the parent div. We seriously need a better versioning for this library, where the clients can lock in the version that works for them.
Moreover, can you communicate the expectation for this library, is this production ready? On Monday, February 23, 2015 at 1:49:04 PM UTC-5, Daniel LaLiberte wrote: > > Dimitry, in the interest of defensive programming, I guess this is a case > where we will have to prefix every css class name with our library-specific > name, but I was hoping to move away from such verbosity. A short prefix > like 'gviz-' would be better. Alternatively, we could obfuscate all the > css class names, though I would really rather not do that. > > > On Mon, Feb 23, 2015 at 1:02 PM, Dimitry Kudryavtsev <[email protected] > <javascript:>> wrote: > >> Hi Daniel, >> >> Thanks for the feedback. I might have found and solved the issue we are >> having. It looks like .hidden class is also part of Bootstrap that was >> setting the display property to none with !important as such: >> >> .hidden { >> display: none !important; >> visibility: hidden !important; >> } >> >> I added the following to my css and it fixed the miss alignment of the >> table headers. >> >> .google-visualization-table .hidden { >> display: table-row-group !important; >> } >> >> On Monday, February 23, 2015 at 12:01:48 PM UTC-5, Daniel LaLiberte wrote: >>> >>> Dimitry, the duplicate tables created when there are enough rows, for >>> the frozen header and body, should have the same cell contents, and the >>> same width and height properties, so they should all end up aligned >>> properly. The way tbody is hidden, using visibility:invisible, means that >>> the size of the cell contents should be the same but just not visible. If >>> it doesn't work for some cases, I would like to learn the details so I have >>> a chance of making it work. Perhaps there is a browser difference. >>> >>> There is a very large number of combinations of the dozen or so options >>> that affect table chart layout, and I admit, we broke some common use cases >>> with this release. We are adding more test cases to be sure this doesn't >>> happen again, but I'll need to find out what additional test cases should >>> be covered. >>> >>> >>> >>> On Mon, Feb 23, 2015 at 11:27 AM, Dimitry Kudryavtsev <[email protected]> >>> wrote: >>> >>>> I did some more digging around and I think I found the issue. This >>>> happens when there is enough data in the table where you need the scroll. >>>> In this case, there are two tables created one that contains fixed header >>>> and the other one that contains the scroll header. The scroll head is >>>> miss >>>> aligned with the width of the data cells. What I noticed is that the >>>> scroll table has hidden property on tbody, if I remove this property the >>>> scroll headers become correctly aligned. So definitely a issue with the >>>> new release. >>>> >>>> >>>> On Friday, February 20, 2015 at 8:33:48 AM UTC-5, Greg Almond wrote: >>>>> >>>>> It looks like there are a few issues arising from the V41 release. As >>>>> of yesterday I noticed that visualization table chart headings are >>>>> misaligned with their corresponding columns of data when the 'height' >>>>> option is specified. This does not occur when the height option is absent. >>>>> I'm assuming that this is related to the V41 changes made to the table >>>>> chart header. Has this issue already been pointed out, and is it being >>>>> considered in the set of fixes being prepared? >>>>> >>>> -- >>>> 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] >> <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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] <javascript:> 5CC, Cambridge MA > [email protected] <javascript:> 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.
