Closed
Bug 193928
Opened 23 years ago
Closed 23 years ago
Make CR or LF function as "search again"
Categories
(SeaMonkey :: Find In Page, enhancement)
SeaMonkey
Find In Page
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: owen.marshall+bmo, Assigned: aaronlev)
Details
Spun off bug 198274.
"CR or LF: search again, that is, search for the next match of the
current search string."
![]() |
||
Comment 1•23 years ago
|
||
bug 198274 does not exist yet.... Is that the right bug number?
Note that we have Ctrl-g as a shortcut for this already and that enter should
trigger the link if the text you find is in a link. So its use for "search
again" would be very inconsistent (it would search again unless the search
result was in a link).
Comment 2•23 years ago
|
||
[shift]+F3 also exists to repeat searches.
i'd be tempted to wontfix this.
Reporter | ||
Comment 3•23 years ago
|
||
Sorry, sorry, this was spun off bug 189274.
Reporter | ||
Comment 4•23 years ago
|
||
Look at that bug, so was I =) I just wanted to get others opinions. Consistency
is good and all. I stand with good company, it seems.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Is anyone sympathetic to the idea of making the "/ <enter>" sequene find the
next search? Although Shift-F3 and Ctrl-G both already do this as was pointed
out, both of these combos are keys which are rather far apart spatially and
which, by using modifier keys, must be pressed together. In the interest of
accessibility, it would seem to be rather harmless to bind "/ <enter>" to the
same functionality. There is a long precedent for exactly this in vi. Also,
the / indicates the beginning of a FAYT search so it would be quite reasonable
to assume if the user hit slash followed immediately by Enter then the next
match was wanted.
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•