Closed Bug 234972 Opened 21 years ago Closed 10 months ago

Find and Replace should operate on current selection only (if any)

Categories

(Core :: DOM: Editor, enhancement, P5)

enhancement

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: mnyromyr, Unassigned)

References

(Blocks 1 open bug)

Details

The Find and Replace function of the mail editor does care about selections made by the user, but it should. :)
Hmpf. :( I meant: Find and Replace does currently *not* care about selected text.
OS: Windows 2000 → All
Hardware: PC → All
Product: MailNews → Core
I'm presuming this bug means that search/replace should be *limited* to the selected portion. "Honor" is a pretty vague term in this context. Is this MailNews:Composition, or Editor?
*** Bug 246640 has been marked as a duplicate of this bug. ***
The bug is also in Composer, thus moving to Editor. Also stealing summary parts from fantasai. ;-)
Component: MailNews: Composition → Editor
Summary: Find and Replace should honor current selection → Find and Replace should operate on current selection only (if any)
Certainly this should be the default, but rather a radio-box option in the find and replace dialog.
Blocks: 323166
QA Contact: esther → editor
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority and severity.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5

I just wanted to submit a new bug and found this one : still in 91.4.1, when editing an email, highlighting some text and then opening the search and replace window, there is either no text or some old text in the find box, not the text that was highlighted in the email editor.
This is so standard in so many programs that I really was quite astonished that it does not work like this in TB

Cheers

Oliver

The original request of this bug was for applications, which is a very different scope of the current DOM:Editor component.
I created a new https://bugzilla.mozilla.org/show_bug.cgi?id=1885833 in Thunderbird to track this feature request.

No longer blocks: 1885833
Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.