Bug 26105 - Webkit becomes unresponsive when keys are pressed within a browser window
Summary: Webkit becomes unresponsive when keys are pressed within a browser window
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.5
: P3 Critical
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-31 08:44 PDT by Francois Hensley
Modified: 2009-07-18 00:27 PDT (History)
0 users

See Also:

Attachments
Website before keys pressed (80.35 KB, image/png)
2009-05-31 08:51 PDT, Francois Hensley 		no flags Details
Website after keys pressed (84.41 KB, image/png)
2009-05-31 08:52 PDT, Francois Hensley 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Francois Hensley 2009-05-31 08:44:57 PDT 
This bug affects the nightly build as well as safari 4 beta 1 and 2. On an intel mac (core duo(32 bit) NOT core 2 duo(64 bit) , ie 1st gen macbook pro), when browsing, and pressing a alphabetic character ie, a-z without doing cmd+f, the browser contents are grayed as if being selected and the browser becomes unresponsive. With the nightly release this has become worse though as when selecting a value in a drop down box, and then pressing TAB, the same happens.

To replicate, browse to any page with or without drop downs, select an area in the page, and then press any key a-z as if you want to start searching for a word without pressing cmd+f first.

Details of machine :
2.16GHz Intel Core Duo
2 GB 667 MHz DDR2 SDRAM
OS X.5.7
Comment 1 Francois Hensley 2009-05-31 08:51:20 PDT 
Created attachment 30815 [details]
Website before keys pressed
Comment 2 Francois Hensley 2009-05-31 08:52:08 PDT 
Created attachment 30816 [details]
Website after keys pressed
Comment 3 Francois Hensley 2009-07-18 00:27:47 PDT 
Looks like this was a safaristand issue.