Closed GoogleCodeExporter closed 9 years ago
I just noticed that the timing for pressing 'g' then 'o' seems to be important
for reproducing the problem. If to press 'g' and 'o' very quickly one after
another the navigation seems to be working fine, however if to press 'g', wait
a second (or even longer) and then press 'o' the described problem occurs.
Original comment by edwin.ke...@gmail.com
on 24 Jun 2010 at 5:42
This is the GWT hosted mode debugger, which is
doing some really weird stuff with the JS event
processing in the browser in order to run Java
code during a JavaScript event. I'm almost not
surprised something broke here.
I'm not likely to spend time trying to track it
down. The 'g-then-o' code works by scheduling a
timer for 250 milliseconds that captures following
keystrokes looking for the 'o' match. If one isn't
received, its supposed to reset the keyboard to the
root level map.
What is probably occurring here is the timer gets
stuck somewhere between the browser code and the
Java backend that is running the emulated UI, and
the whole thing just deadlocks. More than likely
this is a bug in Google Web Tookit.
Just don't use 'g-then-o' in hosted debug mode; if
you need to test that stuff compile to JavaScript
and run under the real Gerrit daemon, without the
GWT hosted mode browser hacks.
Original comment by sop@google.com
on 24 Jun 2010 at 9:46
Original issue reported on code.google.com by
edwin.ke...@gmail.com
on 24 Jun 2010 at 5:26