BUG: Selecting The Same Spot Twice Shows Different Results In The Select Event Sample about google-ajax-examples HOT 3 CLOSED

This is not a bug, it reflects the following behavior. 

The user can select any row (or group of rows using ctrl/shift) in the table 
using a mouse click. When the 
table gets a click event on row i it turns row i to be selected and changes its 
color. However, in case the row is 
already selected the user click is regarded as an un-select event. In the later 
case, row i color is changed back 
to its normal color and row i is no longer selected.

In the example, once you click the same row twice the table selected rows set 
becomes empty and you are 
receivning and appropriate message.

And the fact that when you re-order the lines (by clicking on a header cell) 
and click on of 
the rows, it still says you clicked row # where # is the original row #?

The selection logic in the table is based on the original data table passed to 
the visualization. The table may 
display the rows in a different order but the original order is the one being 
counted for in the selections.

The idea here is that two visualizations may sync on the same dataTable and 
listen to each other's select events, 
yet, without knowing the display order being used in the other visualization.