486985 - Typing before page loaded causes keys to be ignored when loaded

Status: RESOLVED DUPLICATE of bug 466994

(SeaMonkey :: General, defect)

Description

[Aaron Holland]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090223 SeaMonkey/2.0a3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090223 SeaMonkey/2.0a3

Begin to load up a page, e.g. Google, and start typing before the page is fully loaded.  When page becomes loaded all key presses are ignored, both in the input fields and the browser location bar.
Only reloading the page solves the problem.  This is 100% reproducible.

Reproducible: Always

Steps to Reproduce:
1. Begin to load up a page, e.g. Google, and start typing before the page is fully loaded.  
2. Try to type in the search box, or in the location bar
Actual Results:  
No characters appear.  Clicking with the mouse in the location bar or the input fields and then typing does not do anything.

Expected Results:  
Text should appear as you type

Comment 1

[Serge Gautherie (:sgautherie)]

Can you reproduce with Firefox v3.1b3 ?

Comment 2

[Aaron Holland]

No, I just downloaded FF 3.1b3 and this does not happen.  This only happens in Seamonkey 2.0a3.  I believe it's starts to do a text search on the page and clicking on input boxes/location bar does not get you out of it.

Comment 3

[Jens Hatlak (:InvisibleSmiley)]

I think this is a duplicate of either bug 466994 or bug 470175, both of which have been fixed before SM 2.0 was released.

Aaron: Do you still see this with SM 2.0 or later? If not, please change the status of this bug to RESOLVED/WORKSFORME, or, if you are sure it's exactly the same as one of the two bugs I cited, use the Mark as Duplicate link at the end of this page (when logged into Bugzilla).

Comment 4

[Aaron Holland]

Yes, this issue is now fixed, and is indeed a duplicate of 466994, although I didn't realise it was due to search in page feature at the time ( i.e. I did check to see if there was similar issue before logging it ;) ).