bug 20893 comment 3 makes some points in favor of this request.

simon wrote:

Agreed. With the current UI, there is no way to find, and the replace that which has been found. By contrast one can find, and then replace_next, which replaces some random item you've not yet seen, somewhere lower down the page. Bizarre.

• Bug 24327 has been marked as a duplicate of this bug. ***

Bug 24327 is essentially a dupe of this one, but its description summarizes the problem very well:

In the search & replace dialog a "Replace and find next" button would be much
more helpful than the "Replace next".

I support this request. This has been a interaction design issue for a very long time. It is very strange that the usability team made such a blatant mistake, as the rest of the features they produced doesn't contain such blatant mistakes.

I would very much like to see this one fixed.

mhershberger wrote:

Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734

Created attachment 9055
Patch to fix the problem. Should be tested.

"Replace next" now replaces the currently selected text instead of finding the next occurrence and replacing it.

To keep the location of the current occurrence, i added matchIndex to $(this).data.

I added some comments renamed a couple of variable for readability:

• s to textRemainder
• replace to actualReplacement

This is my first significant jQuery-style patch so it may have embarrassing mistakes - constructive criticism is welcome.

Attached:

Committed in r96944.

• Bug 32062 has been marked as a duplicate of this bug. ***

(In reply to comment #8)

Committed in r96944.

Followed up in r101339: renamed "Replace next" button to "Replace".