507444 - Find in page doesn't warn about wrap around after going through whole page once on certain sites

Status: RESOLVED WORKSFORME

(SeaMonkey :: Find In Page, defect)

Description

[Martin F.]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1

The find in page function does not warn that it hasn't found anything (and therefore will start all over again) after going through a whole page on _some_ websites. Examples:
Does not work: http://esd.cs.ucr.edu/labs/tutorial/ (e.g. search for "plex" (without the quotes))
Does work: http://monoteque.de/ (e.g. search for "llt" (without quotes))

Reproducible: Sometimes

Steps to Reproduce:
1. Visit a page
2. Start a find in page with multiple occurrences
3. Keep hitting the button to search for the next hit.
Actual Results:  
On some websites there's a warning that nothing was found before wrap around, on others there isn't.

Expected Results:  
Always displays a warning before wrapping around.

Comment 1

[Arno Teigseth]

In 3.6.8 on Ubuntu 9.04 this works well for me even searching for plex on http://esd.cs.ucr.edu/labs/tutorial/.

But it does NOT wrap around when showing XML files directly (open whatever XML file with firefox and the search stops at the last occurrence)

Comment 2

[Jens Hatlak (:InvisibleSmiley)]

Whatever the issue might be with SM 2.0 search, I cannot reproduce it with the findbar (SM 2.1pre), thus marking WFM. Please only reopen if you can reproduce with a current SM 2.1 trunk nightly (or SM 2.1b1).

Comment 3

[Arno Teigseth]

Jens: did you try on an XML file? 

The wraparound works on the html page with firefox 3.6.12 on ubuntu, but NOT on XML files. OK maybe that should go into another bug.

Comment 4

[Jens Hatlak (:InvisibleSmiley)]

I can confirm that wrap-around doesn't work with XML files (tried http://planetkde.org/foafroll.xml) with SM trunk, but as you said, that's for another bug. Please search for or open one for Firefox, though, since if you see it there, your chances of getting it fixed there are higher than for SM (just stating the truth). Let's keep this one limited to normal web pages.