RESOLVED FIXED 9640
GMail Editor: window.focus() called on keyDown 
https://bugs.webkit.org/show_bug.cgi?id=9640
Summary GMail Editor: window.focus() called on keyDown
Justin Garcia
Reported 2006-06-28 15:18:41 PDT
The arrow keys change focus to the Subject: field instead of moving the caret around.
Attachments
Add attachment proposed patch, testcase, etc.
Justin Garcia
Comment 1 2006-06-28 16:58:20 PDT
On keyDown, GMail calls window.focus(), which focuses the main frame, which kills the selection in the editable frame. Why are they calling window.focus()?
David Kilzer (:ddkilzer)
Comment 2 2006-07-12 21:58:24 PDT
GMail is Google.
Chris Petersen
Comment 3 2006-10-16 12:37:47 PDT
Yes, I'm running into this problem too. Pressing "< " (home) or ">" (end) places focus out of the message body field and puts the caret in the TO field. Same thing happens when pressing ctrl-"<" or ctrl-">" in attempting to move the caret to the start or end of line. Very annoying...
Justin Garcia
Comment 4 2006-10-30 18:02:11 PST
*** Bug 10988 has been marked as a duplicate of this bug. ***
Justin Garcia
Comment 5 2006-10-30 18:04:03 PST
*** Bug 11298 has been marked as a duplicate of this bug. ***
Justin Garcia
Comment 6 2006-11-08 17:25:47 PST
Confirmed that the arrow key problem goes away when I comment out the call to frame->focus() in KJSWindow::focus.
Justin Garcia
Comment 7 2006-11-08 17:27:45 PST
Confirmed that 10988 works correctly when I comment out the call to frame->focus() in KJSWindow::focus.
Justin Garcia
Comment 8 2006-11-08 17:28:37 PST
Ditto for 11298.
Justin Garcia
Comment 9 2006-12-13 15:45:19 PST
This is in radar as <rdar://problem/4810960>
Michael Davidson
Comment 10 2007-01-12 09:32:52 PST
I think this is a WebKit bug. Repro here: http://bantha.org/~mdavids/safari/safari.html Inside the iframe, key events like 'a' and 'b' only trigger the inner event handler. But arrow keys and Cmd-A trigger both error handlers. This is why you're seeing that behavior in Gmail.
Justin Garcia
Comment 11 2007-01-15 19:16:18 PST
r18875
Note You need to log in before you can comment on or make changes to this bug.