commit 0c8ad8e5721775bf03c8cfb4f1e4ffff6dda32ac
author jlabanca@google.com <jlabanca@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Wed Jan 26 13:22:54 2011 +0000
committer jlabanca@google.com <jlabanca@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Wed Jan 26 13:22:54 2011 +0000
tree c21c36ccde15c9377135462756a1e3fce522a16f
parent f10e60ed732f71433f1569e8cccc22062b5dcaf9

Fixing a bug in CellBrowser where the user must click on an element twice to focus on it and enable keyboard support.  The problem is that Element.getTabIndex() returns 0 for non-focusable divs, which causes us to assume that the div is focusable.  Other browsers return -1 for non-focusable divs.  Unfortunately, there is no good way to fix the bug in Element.getTabIndex() because the only way to determine if an element is natively focusable, such as a text box, is to compare the element tagName to a list of known natively focusable element, which isn't scalable.  For now, I worked around it in CellBasedWidgetImpl.

Issue: 5916

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

Review by: rchandia@google.com

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