Open Bug 120568 Opened 23 years ago Updated 14 years ago

Find/Replace should be available for text fields in Navigator

Categories

(SeaMonkey :: UI Design, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: mpt, Unassigned)

References

Details

(Keywords: access, helpwanted)

Attachments

(2 files, 2 obsolete files)

Build: 2002011508, Mac OS 9.1

To reproduce:
1.  Go to any Web page with a TEXTAREA in it, such as the message composition
    area in your Webmail account.
2.  Type a long and rambling love letter to Laura, who you met last night.
3.  Remember that her name was Linda, not Laura.
4.  Choose `Edit' > `Find/Change...', to change all occurrences of `Laura' to
    `Linda'.

What happens:
4.  You can't.
Nice steps to reproduce :-)
Status: NEW → ASSIGNED
Target Milestone: --- → Future
This is a duplicate; hopefully akkana or kin will know what bug #.
Whiteboard: DUPEME
sure sounds like it...

*** This bug has been marked as a duplicate of 76374 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
This was filed in response to comments asking for a separate bug on textareas
(leaving that bug on the <editor> widget).  See bug 76374, comment #12
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Whiteboard: DUPEME
ah, okay then!
FYI, the HTML Source editor in composer *is* a textarea, that's why there is no
find or replace functionality.
mass moving open bugs pertaining to find in page/frame to pmac@netscape.com as
qa contact.

to find all bugspam pertaining to this, set your search string to
"AppleSpongeCakeWithCaramelFrosting".
QA Contact: sairuh → pmac
*** Bug 121988 has been marked as a duplicate of this bug. ***
*** Bug 124989 has been marked as a duplicate of this bug. ***
*** Bug 144521 has been marked as a duplicate of this bug. ***
*** Bug 156246 has been marked as a duplicate of this bug. ***
See also bug 58305, "Find in page ignores text fields".
Blocks: 76374
*** Bug 173437 has been marked as a duplicate of this bug. ***
*** Bug 185963 has been marked as a duplicate of this bug. ***
QA Contact: pmac → sairuh
->kin, +helpwanted...
Assignee: blaker → kin
Status: REOPENED → NEW
Keywords: helpwanted
this enhancement would make http://doctor.mozilla.org much easier to use.
This file was requested by brade, possibly as a patch (I couldn't find the
original version of the file on my disk, so I apologize if that is the case). 
The parameters are incorrect and the nsWebBrowserFind is not being passed as a
parameter correctly.
Attachment #144586 - Attachment filename: EdReplace.js
Attached file EdReplace.js
This is a cleaner version of previous file with all the extra junk thrown out,
sorry for any repeat emails ...
Attachment #144586 - Attachment is obsolete: true
Modification of attachment posted to Bug 58305.  I haven't yet figured out how
to make this into a full-fledged extension, or how to change all the names from
"sample" to "findintextarea" or something more relevant.  Any help would be
much appreciated. I have been merely replacing the jar installed from the
attachedment with this modification.

Seems to work, although code is rather ugly.
If anyone installs this and comes across any problems, please contact me to let
me know.
Attachment #145189 - Attachment is obsolete: true
Keywords: access
Product: Core → Mozilla Application Suite
I take it the findintextarea extension no longer works in current versions of
Mozilla?  I have long wanted this feature, and finally thought to look for a XUL
extension and found the one in this bug report, but I installed it in 1.7.7 and
closed and restarted the browser, but no Replace option has been added to my
Find dialog...
Summary: Find/Change should be available for text fields in Navigator → Find/Replace should be available for text fields in Navigator
FYI, the inability to find text (nevermind replacing it) on a MediaWiki edit page (which uses an HTML form for its edit window) in Firefox, when Opera has no problem with this, is probably the #1 reason *not* to use Firefox for Wikipedia and other wiki work, IMHO. Please consider this in determining when to add this capability to the released products. Thanks.
I received the following info by email (name withheld because they don't appear in the emails listed at the top):

===========================
The <the inability to find text> bug was fixed, I noticed, some time 
ago.  What version of FF are you using?  On what platform?
See attached screen shot showing it working in 2.0.0.2 with MediaWiki.  
(No Replace tho.)
Please reply to the bug if I'm right, or me if I'm wrong.
===========================

(Image omitted.) I am using Firefox 1.5.0.7, and it is still not working. But if it has been fixed and released into the product line in *any* version, shouldn't it say so at the top? Right now, the heading of this bug states the following:

===========================
Status:             NEW
Severity:           enhancement
Priority:           --
Target Milestone:   Future
===========================

Pardon me if I am misintepreting this, but it looks to me like there is no plan to include this enhancement in any specific version of Firefox in any specific timeframe. If it *has* been included, shouldn't that information be made clear at the top, along with what versions it applies to? The only suggestion of any potential fix seems to be in Comment #22 above, which implies *something* was working in *some* version, but wasn't later.
Hi Jeffrey. Yes, searching in text fields works in Firefox 2.x, you're using a rather ancient version (only supported with security fixes until April 24, 2007. Time to ponder an upgrade). This bug is filed against the browser suite (aka Seamonkey), I don't know about the current status of this enhancement for Seamonkey. For Firefox see bug 340942 which would need a bit of love as well. It looks as if demand for search&replace has become lower with the availability of searching alone in text fields.
Component: XP Apps: GUI Features → UI Design
Assignee: kinmoz → jag
QA Contact: bugzilla
Target Milestone: Future → ---
Assignee: jag → nobody
QA Contact: ui-design
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: