commit f3fb5bb7b9c130f5291d1c24d81f20493dafab72
author jlabanca@google.com <jlabanca@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Fri Jul 16 14:18:14 2010 +0000
committer jlabanca@google.com <jlabanca@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Fri Jul 16 14:18:14 2010 +0000
tree 5b4dcf51962d8de333b20efce49fc0adf1c7b5c9
parent bb3faaba48adc3d6ee65633e6216f318fe121bf5

CellTable#onBrowserEvent finds the TD element in which an event occurred, and then assumes that the TD has a parent TR and TBODY. This is normally a safe assumption because browsers only fire native events on elements that are attached to the page, which means a TR and TBODY is present. However, if a the user selects a new value in a select element inside the table, a change and mouseup event both fire, even if the table is refreshed on the change event.  In practice, if a user changes a value onchange and refreshes the table, the mouseup event will fire on the old TD, which is no longer connected to the table.  As a result... this patch checks that both the TR and TBODY are not null.

Review at http://gwt-code-reviews.appspot.com/695801

Review by: rjrjr@google.com

git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@8385 8db76d5a-ed1c-0410-87a9-c151d255dfc7