[Cc'ing John as he is the owner for keyboard-related issues 1061 and 1529]
Issue 3753 has been reported a few hours ago. http://code.google.com/p/google-web-toolkit/issues/detail?id=3753 When I saw it, I immediately thought "this is a dupe" and "we all know what should have been done, it's just a problem with backwards compatibility of GWT apps that justifies GWT is still broken". So I searched the issues and didn't actually find what I remembered sawing in a PPK presentation earlier this year (see my comment on the issue for pointers and the "what GWT should have done" thing). My proposal: - fix KeyPressEvent::getCharCode - do *not* fix the fact that FF and Opera do not follow the IE/Safari model (AFAICT, the W3C has finally settled on a model very similar -- if not identical-- to the IE/Safari one) - fix NativeEvent::getKeyCode (actually DOMImpl::eventGetKeyCode) not no longer use event.which (see https://developer.mozilla.org/en/DOM/event.which ) and eventually add a NativeEvent::getCharCode to back KeyPressEvent::getCharCode. - eventually take advantage of the deferred binding already in place on DOMImpl to use either e.keyCode or e.charCode for getCharCode (eventGetCharCode?) instead of (e.keyCode || e.charCode) Any thoughts? --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
