FWIW, this was the original report:

https://code.google.com/archive/p/google-web-toolkit/issues/8463
https://github.com/gwtproject/gwt/issues/8447

It was one of the reports branched from:

https://code.google.com/archive/p/google-web-toolkit/issues/8228
https://github.com/gwtproject/gwt/issues/8218

On Friday, February 9, 2018 at 10:28:37 AM UTC-8, Jim Douglas wrote:
>
> This ended up being the critical clue:
>
> https://msdn.microsoft.com/en-us/library/ff975945(d=printer,v=vs.85).aspx
>
> ...plus a lot of tedious jsfiddle attempts to dial in the precise method 
> signature.
>
> On Thursday, February 8, 2018 at 12:48:39 AM UTC-8, Thomas Broyer wrote:
>>
>> Apparently, on IE one could use initKeyboardEvent (
>> https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent), and on 
>> "modern browsers" one should rather use the constructor. 
>> Key/keyboard event handling is such a mess… and synthesizing those events 
>> is almost useless anyway… 
>> There's an issue about better keyboard event handling, that's been open 
>> for years. It'd be so time-consuming that it's probably worthless (YMMV)
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to