241484 - leading/ending space confuses find when searching tables

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[Alexei P]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421

Searching backwards for something like " 4/" with the leading space fails even
if the patern exists and had been found with unchecked "search backwards". I did
scroll down before and clicked. Without the leading space it seems to work.
I used an FTP site file file listting page. 

Reproducible: Always
Steps to Reproduce:
1. goto ftp://updates.redhat.com/9/en/os/SRPMS/
2. Find on this page " 4/"
3. Progress forward... 
4. U-turn with "Search backwards"... 

Actual Results:  
"Text you entered was not found" which is not true.. it's still there

Expected Results:  
Search shoud work with leading spaces even going backwards.

Comment 1

[Jesiah S]

I see this with LInux 2004060105 except it is only confused when there a table
and no space.  If you search for " KB" it will work forwards and backwards. 
This also happens in reverse when you search for "03 ".  It will work backwards
but not forwards.

Comment 2

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420