Closed Bug 281534 Opened 20 years ago Closed 20 years ago

Typeahead find should give number of matches in find toolbar

Categories

(Toolkit :: Find Toolbar, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 257061

People

(Reporter: joshgold, Assigned: bugzilla)

References

()

Details

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 Using typeahead find with the new toolbar, I'd like to be able to see the number of matches in the page. Currently on a long page, I find I C-g again and again, looking at the scrollbar to give myself an approximate sense of how many matches (and where they are). Additionally, it could be nice (although I'm not sure how much I'd make use of this latter cue) to see *which* match is presently selected (e.g., 4/20, with the 4 incrementing on every C-g) Reproducible: Always
I know we don't like preferences, but can I vote against this bloat of a quick and simple feature (or make it a preference). If you want to look at 4/20 rather than the page then can we have this in a floating window with all search features. The typeahead find should be as simple as the last line mode in vim. Tap the '/' key and go. You really only need additional information if the string is not found. Usually if you are searching within a page, you want the search operation to centre it on a single point of interest; not a forme fruste of a 'find all'
I see your point, and it's true that I want to center on one point of interest. I was surprised when firefox introduced the toolbar with those big buttons, myself. It's not find all that I need, though. I want help *finding* the right place in the document. (Like you said, you only need additional info. when the string is not found. -- I'm talking about the situation where firefox finds strings, but I'm still looking for the information I want.) In long documents, I find my practice is to hit C-g rapidly to see if the right thing pops out. Often I'll realize after a while that I've wrapped around without having noticed (or that I'm not sure if I've wrapped). Once I've realized this, I'll C-g my way through once or twice more,staring at the scrollbar to see how many "hits" there were, at which point I have a better idea of how carefully to look and whether I'm likely to find what I'm looking for at all. I want to skip that step. At any rate, I don't think a number or a ratio in plain text at the right hand side of the already extant toolbar would clutter, and I would never want to go back to a floating window!
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/
*** This bug has been marked as a duplicate of 257061 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.