Thanks thomas ,the workaround works but we need to replace 13 with 10
in line :
} else if (charCode == 13) {
doOnEnterKeyPressed();
}
it should be:
} else if (charCode == 10) {
doOnEnterKeyPressed();
}
with this new change code works both in chrome and FF3.
and i can't understand why some people try to divert the discussion
into Date formating futilities!
thanks thomas.
On Jan 12, 8:06 pm, Thomas Broyer <[email protected]> wrote:
> The changeset you link is actually exactly what causes the current behavior
> in Firefox.
> Seehttp://code.google.com/p/google-web-toolkit/issues/detail?id=5003#c1for the
> rationale,
> andhttp://code.google.com/p/google-web-toolkit/issues/detail?id=5558#c6for the
> workaround/fix (i.e. only use getNativeEvent() when getCharCode returns 0).
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
