Open
Bug 347261
Opened 20 years ago
Updated 4 years ago
/ FAYT should invoke Find rather than QuickFind
Categories
(Toolkit :: Find Toolbar, defect, P5)
Tracking
()
NEW
People
(Reporter: myk, Unassigned)
References
Details
Although ' is a fundamentally different kind of search, / is functionally the
same as regular find (i.e. it searches through the exact same text and
highlights/focuses matches in the same way), and nothing in regular find makes
it less usable than / for accessibility-focused users.
So there's no downside to making / start a regular find instead of a quick
find, and there's plenty of upside (f.e. the "Highlight All" option and a clear
message when the text isn't found).
It does make sense to continue to differentiate ' from regular find, however, since that really is a different kind of search (in fact, we might want to differentiate it further by calling it something like "link find").
Bug 347259 is about making autostart FAYT start regular find instead of quick find. But given the benefits of doing so, we should also make / start regular find.
My proposal (bug 347259) was not that / invoke Find, that and ' should remain with the accessibility focused QuickFind. Otherwise, changing / would be undoing half of what bug 337654 accomplished. The only case I am talking about changing is when "Search for text when I start typing" is turned on in preferences.
According to some discussion in the forum threads mentioned in bug 347259, there are some minor differences in the way the Find bar and the QuickFind bar work. I don't know all the details, but one main one is how fast the QuickFind bar fades out. For accessibility, a fast timeout may be very useful as it doesn't keep the user "trapped" in the find bar.
Comment 2•20 years ago
|
||
See also bug 346400, "Make quicksearch not take up the entire width of window". That will only apply to /, not Ctrl+F, so it kinda conflicts with this bug.
Comment 3•20 years ago
|
||
*** Bug 354001 has been marked as a duplicate of this bug. ***
Comment 4•20 years ago
|
||
*** Bug 356055 has been marked as a duplicate of this bug. ***
Comment 5•20 years ago
|
||
*** Bug 356958 has been marked as a duplicate of this bug. ***
Comment 6•20 years ago
|
||
*** Bug 357707 has been marked as a duplicate of this bug. ***
Comment 7•20 years ago
|
||
any news on whether we're gonna get back our buttons for quick find? it's totally useless to me now, and I was using it *extensively*. thanks
Comment 8•20 years ago
|
||
I liked the old behavior, pre 337654.
But if you 'need' to have things visually different, why not just make the buttons that were removed without text lables, and leave the 'quick find' label.
OR, make quick find appear in a different pat of the screen. Perhaps centered at the top. I like QuickFind/FAYT clearing after 5 secs so I don't like changing the preference.
All I really need is 'Highlight All' back in FAYT. Please Fix This !!!!
The addons sections of the Mozilla website has just the thing to fix this problem. Download and install a copy of FAYT_1.0.0.1.xpi and / brings up the quick find bar with the find previous and next and "highlight all" options - just like it used to.
Regards,
Adrian
Comment 10•19 years ago
|
||
Thanks Adrian ! I'm just happy to see the old find behaviour !
I just had a hard time finding this extension in the Firefox addons site. Expecting other people would read your comment, I'm adding this few precisions : it's named simply "FAYT" and you can find it at https://addons.mozilla.org/firefox/3650/.
Comment 11•19 years ago
|
||
I wanted to add the same.
Try this in your userchrome.css.
/* Restore quick find bar */
#FindToolbar > * {display: -moz-box; }
Bye,
Nick
Comment 12•18 years ago
|
||
Excellent extension.
I can see why the default FAYT bar might be made more simple, but when you've manually checked, that you want to search when you type, the bar really should be with buttons.
Comment 14•18 years ago
|
||
This need to be re-considered, together with FAYT w/o "/".
Every other browsers is enhancing the quick search, whats the reason behind the change of crippling firefox's quick search again?
Comment 16•18 years ago
|
||
Find as you type should still fade after a while, but it should have all the functions that a proper find has. After all, the whole point of enabling find as you type is to save the effort of pressing ctrl+f. If you need to press ctrl+f sooner or later just to get the full functionality, find as you type is effectively useless.
Comment 17•18 years ago
|
||
(FYI, people who have been using the userChrome.css hack to enable the buttons in Firefox 3 should probably take a look at bug 434305, as that's an issue that has been asked about multiple times in the forums.)
| Assignee | ||
Updated•18 years ago
|
Product: Firefox → Toolkit
Comment 18•18 years ago
|
||
Note that bug 337654 was what made Quickfind look visually distinct from Find, as the dismissal interaction was different. The idea had always been that FAYT invocation was about quickly finding something and then having the UI auto-dismiss.
Not sure if this bug report is asking for FAYT to invoke Find, or for Quickfind to have some of the function of Find, or if it's just to say that ' is FAYT and / is a synonym for Cmd/Ctrl-F.
Comment 19•18 years ago
|
||
Summing up I think it wants:
* When FAYT is enabled in preferences, typing should bring up the real find.
* If it is not enabled, typing should bring up a small OS-like searchbox.
I also think it says, that if the firefox team is not willing to the above, at least FAYT should have a way to browse hits next/previous. With buttons or like in gtk with the scrollwheel.
Comment 20•18 years ago
|
||
What I was thinking this was asking for is that / should be a synonym for ^F. Specifically, the lack of a way to find the next/previous result is what really bugs me. I often find myself searching for some text (with /), hitting alt-n to find the next result, and then wondering why nothing is happening.
| Reporter | ||
Comment 21•18 years ago
|
||
To reinforce what others have said in response to comment 18, my premise in filing this bug is that there is little to no distinction in the eyes of many FAYT users between FAYT and Find.
Perhaps the difference in the dismissal interaction is appropriate, but in other ways the two are treated by many users of both as if they were functionally equivalent, and it is both confusing and frustrating to those users that they are not.
So this bug is asking for / to invoke Find (or something that is functionally equivalent to it, except possibly for the dismissal interaction). This bug doesn't address the behavior of ' (Link FAYT), nor does it address the behavior of Autostart FAYT (that is bug 347259, which I think should also invoke Find, but which has been WONTFIXed).
Comment 22•18 years ago
|
||
When you say that / should invoke find, do you mean the "/" character on the keyboard? Because that is not necessarily very accessible on all local keyboards. I personally have to hold Shift to type it. As a matter of fact I can do Ctrl+F with one hand, but "/" takes them both.
| Reporter | ||
Comment 23•18 years ago
|
||
(In reply to comment #22)
> When you say that / should invoke find, do you mean the "/" character on the
> keyboard?
Yes.
> Because that is not necessarily very accessible on all local keyboards.
There's also Autostart FAYT and regular Find for folks who find / inconvenient. If you think it should be possible to use a different character to invoke FAYT, that's a legitimate request, but please file a new bug report on that, as this report is about changing the behavior of the existing shortcut key.
Comment 24•18 years ago
|
||
It just seams strange to call it find as you type, if you have to press some keys to make it start. I guess with 347259 there is no hope for actual FAYT to invoke find.. Even if you have enabled it in preferences.
Comment 26•17 years ago
|
||
(In reply to comment #22)
> When you say that / should invoke find, do you mean the "/" character on the
> keyboard? Because that is not necessarily very accessible on all local
> keyboards. I personally have to hold Shift to type it. As a matter of fact I
> can do Ctrl+F with one hand, but "/" takes them both.
Doesn't your keyboard have Shift keys on both sides? On mine, / is also shifted, the second-last key of the bottom row, and I can type it quite easily with the index and little fingers of the right hand. For Ctrl-F (with F in the middle of the keyboard, farther away from both Ctrl keys), typing it with one hand is much more awkward.
Comment 27•17 years ago
|
||
This reminds me of something: That ugly thing to the right of the address bar (sort of a useless extra stub), does not even have "Find in Page" as one of its drop-down options.
Firefox "find" in general has been problematic for me, so I currently use Ctrl-F or open the page in a different browser and use that program's "find" tools (or apply a Style filter). Also, even in 3.5.2 pressing Ctrl-F a second time does not close Find. It would be better if Ctrl-F was used as a two-way toggle for Find.
Updated•10 years ago
|
Priority: -- → P5
Updated•4 years ago
|
Severity: normal → S3
Comment 28•4 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 7 duplicates and 17 votes.
:enndeakin, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Flags: needinfo?(enndeakin)
Comment 29•4 years ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Flags: needinfo?(enndeakin)
You need to log in
before you can comment on or make changes to this bug.
Description
•