357799 - Ctrl+F and Ctrl+G are performing the same action

Status: RESOLVED INVALID

(Toolkit :: Find Toolbar, defect)

Description

[kallol]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; Avant Browser)
Build Identifier: Mozilla/5.0

If on a web page the user tries to use the quick search by using Ctrl+F key it is working fine. But, Ctrl+G is performing the same action. Basically, Ctrl+F and Ctrl+G is doing the same thing.

Reproducible: Always

Steps to Reproduce:
1.Open www.rediffmail.com
2.Press Ctrl+F and perform a search by typing 'People'
3.Close the Search area.
4.Press Ctrl+G and perform a search by typing 'People'

Actual Results:  
The search is occuring in the same way. Basically there is no difference between among the two key combinations.

Expected Results:  
Those two key combinations should perform different actions.

Comment 1

[Martijn Wargers (dead)]

There is a difference, when the search bar is already open, and you've searched already something, you can find the next instance with Ctrl+G, not with Ctrl+F

Comment 2

[Ben Fowler]

See Bug 285437 "Ctrl+F when Find bar has focus should Find Again (instead of 
Ctrl+G?)"

If you are on a web page, should not Cmd-F open the search bar and select its contents?

In your 'use case' you should not need to type the search term again - after 
Cmd-G - if you want only to locate the next occurrence.

I agree that the UI should be established to be not confusing and as simple as 
possible; for example Cmd-F to 'Find', Cmd-G to 'Find Next'.

Comment 3

[Martijn Wargers (dead)]

This is not fixed, maybe you agree this is invalid?
Or do you think this bug is a duplicate of bug 285437?
(I know I'm a bit nit-picky, but only bugs that have patches attached and those patches are checked in can be marked fixed)

Comment 4

[Ben Fowler]

Martijn if that is for me, I didn't try to mark this Bug as FIXED, though I 
accept that I may have misused Bugzilla.

FWIW, this bug can probably be fixed/closed by documenting "How to use the 
search bar"  to the satisfaction of the OP (I have found that fixes to 
documentation are  not accepted here); and Bug 285437 is verging on WONTFIX. 
I am more than a little reluctant to make either of those suggestions, mind, 
because the defect (if any) may be platform specific, and I am on a 
minority platform!

Comment 5

[Martijn Wargers (dead)]

No, kallol marked it fixed.
You want to fix it in the help documentation? I think suggested improvements are certainly welcome.

Comment 6

[Chris Blore]

Can we agree that this bug is INVALID or is there another resolution you would prefer?