The options for them are null by default, so having them disabled when they are set to null would force every user to have their own classes to handle the css for pretty much every aspect of the table. If you are using the default styling without the even/odd row striping, then you can "disable" the hover and select styling by giving them class names that don't point to any styles. I was going to suggest using javascript to change the class names back on hover or select, but you could run into timing issues where your custom event handler might execute before the default. Perhaps the better solution would be to have an option that disables the hover or select styling (without using the cssClassNames option).
On Wednesday, March 28, 2012 8:27:05 AM UTC-4, Jeremy Davies wrote: > > Hi, > > I've looked at the forum and understand that the two above class > definitions are applied and all other classes removed when used with > the Table chart. (To support IE6). > > Could I ask that if they are set to "" or null as part of the options > for the chart that the logic that removes and resets the class be > changed to not function. > > This would allow us to effectively remove the support of either of > these features in our implementations that do not require them. > > Cheers, > > Jeremy. -- 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/-/ZAnQMi-xBjAJ. 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.
