Closed Bug 122061 Opened 23 years ago Closed 14 years ago

List all matches in a listbox for page search

Categories

(SeaMonkey :: UI Design, enhancement)

Product:
SeaMonkey
Component:
UI Design
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: netdragon, Assigned: jag+mozilla)

References

Details

Broken off from bug 32641:

When you search, it should make a list of all the matching words in a listbox
with entries that you can individually click on. Norton Systemworks 2000 registry 
editor does this if you need to see an example.
->future
Target Milestone: --- → Future
confirming (especially as this is targeted)
Status: UNCONFIRMED → NEW
Ever confirmed: true
akkana/pmac
Assignee: trudelle → akkana
QA Contact: sairuh → pmac
This is actually a UI design issue; the backend can do this (more gracefully as
soon as I finish the work I've planned this milestone for bug 97157, so I'm
adding a dependency on that bug).  Assigning this one to front-end folks.
Assignee: akkana → trudelle
Depends on: 97157
QA Contact: pmac → sairuh
QA Contact: sairuh → pmac
I don't see the point of listing the find hits.  For most searches, each hit
will be exactly what you searched for.  Highlighting each occurrence in the
original page, as requested in bug 62467, makes more sense to me.
Mass moving all of my open Nav/toolkit bugs to new owner.
Assignee: trudelle → sgehani
Product: Core → Mozilla Application Suite
Assignee: samir_bugzilla → jag
QA Contact: pmac
Target Milestone: Future → ---
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
Status: NEW → UNCONFIRMED
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
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.