279793 - Find incorrectly matches text crossing some element boundaries

Status: RESOLVED WORKSFORME

(Toolkit :: Find Toolbar, defect)

Description

[Johan Prins]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Search string is found across a html element, as far as I can see:

ro<ELEMENT>me

Reproducible: Always

Steps to Reproduce:
1. open URL
2. start typing 'rome'
3. see the bug...

Actual Results:  
highlighted
ro<bullet>me

Expected Results:  
no highlighting

Comment 1

[Johan Prins]

Attachment: See the 'bug' in action

Comment 2

[teklund]

Attachment: Simple Testcase

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Johan Prins]

Bug still present in Firefox v1.07

Seems to be fixed in Firefox 1.5beta1

Comment 5

[Kevin Brosnan]

We don't know what fixed this worksforme