The width method I suggested does work, but I need to see about scrolling/dragging for width versus height differentiation.
I thought this was the purpose of viewWindow, or at Least Explorer. Originally I was using something like 85% width for my chartArea in an attempt to create an adaptable page for all screen sizes, following good design practices. The problem with this is the API will try to jam all columns into that 85%, no matter what the screen size. Since this is a Google API, a company who penalizes websites for not being flexible, it seems appropriate that the API should have some solution for this problem. Such as setting a viewWindow size and panning. -- 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/cbed5f41-3995-46f7-a273-0d675674dece%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
