GWT abstracts many browser discrepancies, but not the fact that Firefox has an awful logic re. keypress events. For Firefox, every key pressed generates a keypress events (whereas others only do so for "printable characters"); which means getCharCode/getUnicodeCharCode will be 0 in those cases. And for Firefox, the Enter key is not a "printable char" (i.e. its getUnicodeCharCode will be 0). There are many issues open in the issue tracker about this change (it didn't work that way in older GWT versions), you'll find the rationale for the change and workarounds there. IMO, you should just use keydown or keyup events instead.
-- 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.
