gp1313 / iep

Automatically exported from code.google.com/p/iep
0 stars 0 forks source link

Change "Enter" Behaviour when Searching #141

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Start a search for any text with Ctrl-F
2. type the word you are searchgin
3. type enter. 

What is the expected output? What do you see instead?
I would excpect, when hitting enter, to go to the next found item. Instead of 
that, a new-line is added. I have to click on 'next' button with my mouse, 
which is quite disturbing/slow

What version of the product are you using? On what operating system?
Latest version on Windows.

Original issue reported on code.google.com by po...@hotmail.com on 28 Dec 2012 at 12:42

GoogleCodeExporter commented 8 years ago
I cannot reproduce this issue on Version 3.1: here the widget behaves as 
desired. I'm on Mac OS X though, but I am not aware of any behavioral 
differences between the platforms. Are you sure you don't have the focus on 
something else when pressing enter? The focus should be on the edit box for the 
enter key to work as you want, which should be the case if you have just typed 
something in the search field.

Original comment by ludo.visser on 28 Dec 2012 at 3:56

GoogleCodeExporter commented 8 years ago
It happens on the *second* time that you press enter. On the first time, the 
find-widget has focus and pressing enter should find the next word. Upon 
finding the word though, the word is selected in the editor and the editor 
gains focus. This behavior is intended.

You can use F3 to search for the next occurrence. I believe this is similar to 
other editors. If not, we should consider giving focus to the editor.

Original comment by almar.klein@gmail.com on 28 Dec 2012 at 9:34

GoogleCodeExporter commented 8 years ago
Marking as invalid. Feel free to reopen if you think the current behavior needs 
a change.

Original comment by almar.klein@gmail.com on 27 Feb 2013 at 3:48