Closed Bug 134529 Opened 24 years ago Closed 23 years ago

Find command sometimes fails to find desired text on page

Categories

(SeaMonkey :: UI Design, defect)

PowerPC
Mac System 9.x
defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: aganley, Assigned: bugzilla)

References

Details

So far I've found a couple of problems when using FIND from the search menu: The most drastic is that it doesn't always work (i.e. doesn't find something that is there). Not clear why some things are found, and others aren't. I only did this on one website (http://rush.genetics.duke.edu/orthologs/index-sorted.1.html), but it worked correctly only 50%. Also, the dialogue box has problems. Sometimes the text already there can't be changed, so you have to close the box and reopen to delete/emend. Sometimes pasting text into the box doesn't work.
Austen, what build are you using? Are you still seeing these issues? What did you search for on rush.genetics.duke.edu ?
Blocks: 70771
Austen, is it possible that you have searched for e.g. "dim1 human" on that page? If so, did you notice that it really is e.g. "dim1_human", only that underscore character isn't visible because it's a link (and links are underlined)?
Austen, please tell us what build ID you're using to report this problem, as requested in comment 1. Also, please report only one problem per bug. Report the second problem (about the dialog) as a separate bug. Thanks. WorksForMe using Mac/2002072203. Searching for "Stajich" successfully found that text at the bottom of the page. Reassigning to XP Apps: GUI Features.
Assignee: sgehani → blaker
Component: Search → XP Apps: GUI Features
QA Contact: claudius → paw
Summary: Problems with the FIND command (maybe related?) → Find command sometimes fails to find desired text on page
Non respondez -> WFM
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
v
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.