331831 - FAYT blocks input fields if keys are typed before page is fully loaded

Status: RESOLVED DUPLICATE of bug 293889

(Toolkit :: Find Toolbar, defect)

Description

[u211322]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

When FAYT is enabled and you load up a page that contains input fields, ,focus the input field and enter some text before the page is fully loaded the text is used like a FAYT search with no possiblity to "unblock" this. The only solution to be able to enter text in the input field is to close the current browser window and retry.

Reproducible: Sometimes

Steps to Reproduce:
1. Enable FAYT
2. Open any page that contains an input field (e.g. http://www.maniac-forum.de/forum/pxmboard.php?mode=messageform&brdid=1)
3. Before the page is fully loaded focus the first text field on the page and type in any text.

Actual Results:  
A find starts on the page with no way to enter text in the input field

Expected Results:  
Text should be entered in the focused input field

It started to happen in release 1.5.0. Never had this problem in a previous build.

Comment 1

[Martijn Wargers (dead)]

You have the option "Begin finding when you begin typing" checked? (under Tools->Options->Advanced)

Comment 2

[Martijn Wargers (dead)]

Testcase with 5 seconds sleep:
http://wargers.org/mozilla/fayt.php
Testcase works for me in current trunk build.

Comment 3

[u211322]

(In reply to comment #1)
> You have the option "Begin finding when you begin typing" checked? (under
> Tools->Options->Advanced)
> 

Yes, that's the option I enabled to be able to use the FAYT feature. I have to say that I absolutely love this feature and I'd hate to have to disable it because of this bug. 

Comment 4

[u211322]

(In reply to comment #2)
> Testcase with 5 seconds sleep:
> http://wargers.org/mozilla/fayt.php
> Testcase works for me in current trunk build.
> 

I tried your testcase and I wasn't able to reproduce the wrong behaviour. 

But now that I think of it it could also be related to frames. The pages where I this problem happens most of the time all use frames (at least 3). 

For example I had it very often when trying to login here: https://asp.wbi.at/wbi/

Comment 5

[Mark Romero]

(In reply to comment #4)
> (In reply to comment #2)
> > Testcase with 5 seconds sleep:
> > http://wargers.org/mozilla/fayt.php
> > Testcase works for me in current trunk build.
> > 
> 
> I tried your testcase and I wasn't able to reproduce the wrong behaviour. 
> 
> But now that I think of it it could also be related to frames. The pages where
> I this problem happens most of the time all use frames (at least 3). 
> 
> For example I had it very often when trying to login here:
> https://asp.wbi.at/wbi/
> 

I was able to confirm the bug with the current build on the second website provided by the reporter (https://asp.wbi.at/wbi/), but not the first, nor the testcase provided by Martijn.

Comment 6

[Mark Romero]

Test Case, 5 second sleep in frame:

http://www.shieldyrbk.com/tgl/mozilla/fayt.html

This works for me with the current build.

Comment 7

[Mark Romero]

(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #2)
> > > Testcase with 5 seconds sleep:
> > > http://wargers.org/mozilla/fayt.php
> > > Testcase works for me in current trunk build.
> > > 
> > 
> > I tried your testcase and I wasn't able to reproduce the wrong behaviour. 
> > 
> > But now that I think of it it could also be related to frames. The pages where
> > I this problem happens most of the time all use frames (at least 3). 
> > 
> > For example I had it very often when trying to login here:
> > https://asp.wbi.at/wbi/
> > 
> 
> I was able to confirm the bug with the current build on the second website
> provided by the reporter (https://asp.wbi.at/wbi/), but not the first, nor the
> testcase provided by Martijn.
> 

Sorry, that is erronous. After further testing I was unable to confirm this bug (even on the wbi.at website)

Comment 8

[Martijn Wargers (dead)]

All testcases are wfm too (with "Begin finding when you begin typing" turned on).

Comment 9

[Jens Pedersen]

I've experienced the same problem even with google.com, that if I start typing before the page is fully loaded a FAYT is started and I'm not able to enter text in any input field. I've always had the problem with Firefox 1.5. Unfortunately I'm not able to reproduce it on a regular basis. 

Comment 10

[Richard Arets]

I've been able to reproduce this bug consistently. When opening a NEW WINDOW and then opening a page from a BOOKMARK, this bug seems to occur every time (p.e. google, yahoo and the above mentioned testcases). This doesn't happen when openening a link in a new window (right-click -> Open in new window).

Comment 11

[Martijn Wargers (dead)]

Richard, can you reproduce this with http://wargers.org/mozilla/fayt.php ?

Comment 12

[Richard Arets]

(In reply to comment #11)
> Richard, can you reproduce this with http://wargers.org/mozilla/fayt.php ?
> 

Well, this gets weirder all the time. I tried this several times with your testcase before I posted my first comment and I could reproduce it every single time. Now, I could reproduce it again several times, but it seems like the more I try, the less it happens...

Comment 13

[Martijn Wargers (dead)]

Well, I still can't reproduce this :(
Richard, do you have extensions installed? Does it happen on a clean profile?

Comment 14

[Luis B. Almeida]

This has happened to me several times, even in google, and on two different computers. One of them has 1.5.0.4 installed, and the other has 1.5.0.3. Both have several extensions installed. I'd hate to have to uninstall all the extensions just for testing this bug, since there's no simple way to disable and later re-enable extensions (but that's a different bug/rfe).

I haven't been able to find a sure way to reproduce this bug, but it has happened to me several times (more than I'd like). I'm not sure whether it happens when you start typing before the page is fully loaded or whether there's some other condition that makes it happen.

I've tried the test case at http://wargers.org/mozilla/fayt.php and it didn't cause the unwanted behavior to happen.

Comment 15

[Glenn Dobbelaere]

As the rest of you guys I have this bug also. It seems not to occur when opening lets say google in different tabs in the same window, it seems to happen when I open Google in one window and then open a new window and then try to type in Google (Even after the page is fully loaded). If this cannot be reproduced, open Google in two different tabs in the same window and type something in the fields, then open a new window and also go to Google and try typing then. (FAYT must be enabled of course). When refreshing the page with overwriting the cache (Ctrl+F5) this problem seems to be resolved for that window you did the refresh in. I also would like to add that I seem to have this problem since version 1.5 and up. Also I have the following extentions installed (might be the problem): ForecastFox, foXpose, Autocopy and PayPal...however I need to add that I had the problem already when only ForecastFox was installed. Hope this error is found soon, it's really annoying.

Comment 16

[Martijn Wargers (dead)]

Glen, I think what you're describing in comment 15 is bug 339465.

Comment 17

[Glenn Dobbelaere]

It sounds very similar, however, when I minimize and maximize my window the problem is not solved for me. I do not know if this problem happens to me if the page has not yet completely loaded like creator of this thread said, because the Google layout is so simple that it loads in a split second, so it is hard to tell. However, i do know that I have this problem even after the page loads completely. I asked a friend of mine if he had the same problem and he did not, he also does not have as many, and the same extentions as I do... It might just be an extention problem, who knows? 

Ok, so now here comes the weird part: I just installed the 'DownThemAll' extention and now I am NOT able to replicate this problem anymore, and before I got it 99% of the time... people might try it out...if this works for others the problem may just be an extention problem after all.

Comment 18

[DaCypher]

This seems to happen to me several times a day now.  I have not yet noticed any consistencies with what causes the problem, however.  I'm actually not even sure if I am seeing this bug or bug 334067 (maybe they are dupes of each other?).

I have no extensions installed and I have even created a new profile (only copied my bookmarks from my old profile) to narrow things down, yet I still experience this problem.  I have also experienced this issue on my laptop that has AdBlock Plus and maybe one or two other small extensions installed.  However, I have never hit this bug on either of my machines at work.  All machines have the 'Begin finding when you begin typing' option enabled.

I only started experiencing this issue after one of the 1.5.0.x releases (it was either 1.5.0.3 or 1.5.0.4, I can't remember).

Hopefully some of this is helpful, I'll post updates if I can narrow things down at all.

Comment 19

[Mike Connor [:mconnor]]

Not going to block on something that remains unconfirmed.

Comment 20

[Martijn Wargers (dead)]

Testcase from comment 2 is now at: http://nova.serverway.net/~mw22/mozilla/fayt.php

Comment 21

[Zac]

I also been experiencing these symptoms frequently (ie. FAYT triggering while I'm trying to type in a text box such as the one here). I haven't worked out what causes this to happen. It could well be something to do with the page not being fully loaded, but I don't know.

I do know that it is always fixed if I minimise and unminimise firefox.

Comment 24

[Tyler Downer [He/Him]]

I don't see this with Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a1pre) Gecko/20090912 Minefield/3.7a1pre (.NET CLR 3.5.30729) ID:20090912042051. Can anyone reproduce with 3.5.3 or later in FF safe mode?