setKeyCode doesn't work in firefox about gwt HOT 24 CLOSED

User has reported same behavior with Opera.

test

test of what?

I am using the setKey funcion myself also and it is failing in Firefox. Is this bug

beeing considered for 1.4?

Opera throws also a DOM exception. I have a patch for this issue that simple does
replace the original setKey method for Mozilla and Opera with an empty method.
Patch is relative to r1292.

Since the keyCode property is read-only in Mozilla, Firefox, and Opera, the
DOM.eventSetKeyCode() method is unreliable for cross-platform coding.  Ignoring the
method call in unsupported browsers is the equivalent of just catching the JavaScript
error and ignoring it, but in either case you have to find a workaround.

I'll search for some possible solutions, but we may end up deprecating the function
if we cannot find a suitable implementation for the other browsers (or at least Firefox).

We may have a solution that works across all browsers for the most common use case of
replacing characters in a TextBox.

Also, while Safari doesn't choke on this, it appears that it doesn't actually change
the value.  That means that the eventSetKeyCode method really only works in IE.

http://groups.google.com/group/Google-Web-Toolkit-
Contributors/browse_thread/thread/b9ba086f35112f62/#

when using a KeyboardListener on a text box, I get this exception a lot : 

java.lang.AssertionError: attribute 'keyCode' not defined for event type 'mousemove'

is this the same problem ?

If you're seeing this assertion, that means someone is calling Event.getKeyCode()
from within a non-keyboard event. Silly as it is that the Event interface allows you
to ask for such things... We added the assertion because different browsers do
different things in this case (including throwing errors) and there's no 'correct'
return value.

ok then maybe I should fill an issue? I have a DeckPanel which choose the widget to
display depending on mouse events. One of the widgets is a text box. 
(what I'm trying to do is a widget that display text infos in a static manner and
that can be edited if clicked on it, kinda like the "edit event" in google calendar)

If you're seeing this assertion, but not explicitly calling getKeyCode() on a mouse
event object, then that sounds like a bug. If this is indeed the case, please file
a
new one and cc me on it so I can have a look.

I've finished my bug hunt. here is the result :
http://code.google.com/p/google-web-toolkit/issues/detail?id=2683

We should deprecate this method as it isn't supported on all browsers, and there
isn't a reliable way to fix that.

http://gwt-code-reviews.appspot.com/2002

committed as r4421

1_6_RC has been released.