From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt) BuildID: 2000101014 I searched for a word in composer in forward direction and after I searched for the same word in backward direction using the option "Search Backwards". The results were not same. With my specific case, I found 16 matches in forward direction and only 12 in backward search. It skiped the following cases: 1.The word that appears more than once in a single line. 2.The words in the table. Reproducible: Always Steps to Reproduce: 1. Open an existing document (or new) in composer. 2. Select Edit->Find... 3. It opens the "Find in this Page" dialog. 4. Enter word to be searched. 5. Place the cursor at the top of the document and continuously click on the Find button till all the occurances are found. 6. Again place the cursor at the end of the document. 7. With the same search word, check the " Search backwards" option. 8. Continuously click on the Find button till all the occurances are found. 9. Compare the results. Actual Results: The results are not same. Expected Results: The results should be same. It should locate all occurances in backward direction also.
assigning to sfraser
Assignee: beppe → sfraser
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → mozilla0.9
i see this as well, so adding self to cc list. also thought i had seen this when "Wrap around" was selected, but i cannot seem to get a reproducible case... if i do, i'll add it here in case it's related to this current issue.
Kin has fixes for find backwards.
Assignee: sfraser → kin
Accepting bug. This will be fixed when I land the new Find and Replace feature.
Status: NEW → ASSIGNED
moving to mozilla0.8, this should land by 19-Jan
Whiteboard: moz0.8, 19-Jan
Target Milestone: mozilla0.9 → mozilla0.8
This should have been fixed by the landing of the Find/Replace feature. (Bug #6254)
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
verified in 1/24 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.