Closed Bug 76374 Opened 24 years ago Closed 22 years ago

no [Find] ([Search]) or [Replace] in HTML source editor for Composer

Categories

(Core :: DOM: Editor, defect, P3)

Product:
Core
Component:
DOM: Editor
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 69329
Milestone:
Future

People

(Reporter: atomic, Assigned: kinmoz)

References

(Depends on 1 open bug)

Details

The find and replace functions don't work in HTML source editing mode.
reporter, what build are you using?
Comments from reporter: Build ID 2001032319
I see this too. BUILD: Linux 2001-04-17-08 STEPS TO REPRODUCE: 1) Open a page in composer 2) Switch to view source mode 3) Open the edit menu EXPECTED RESULTS: the "find" and "replace" options are enabled ACTUAL RESULTS: the "find" and "replace" options are disabled NOTES: This happens, of course, because we use a textarea for the view source mode. However, I would say that it should be possible to find/replace in textareas in general.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: mozilla1.1
OS: Windows 2000 → All
Hardware: PC → All
Summary: No [Find] or [Replace] in HTML Source editor. → No [Find] or [Replace] in HTML Source editor and other textareas
-->kin
Assignee: beppe → kin
Target Milestone: --- → mozilla1.0.1
*** Bug 86828 has been marked as a duplicate of this bug. ***
Highly desirable Change Request! The Replace option in raw HTML editing mode should allow you to search for a block of HTML code over a no of lines and replace it with another block of code again spread over a no of lines. This would make global format changes much easier! The code could be put in the Find and Replace fields using Cut and Paste from the editor. This would also be useful in WYSIWIG HTML editing mode.
*** Bug 100562 has been marked as a duplicate of this bug. ***
Status: NEW → ASSIGNED
Blocks: 106961
*** Bug 109731 has been marked as a duplicate of this bug. ***
As of 11/30/01, this issue is still present. I also like to have the find/replace option in html. I tried to do this as well, and to no avail, was unable to do it. I am using build 2001112603 and win me. I have also tested this with 2 versions of '98. I am posting to let you know that this issue still exists.
Should this bug be assigned to Akkana? Or should it be changed to refer just to textareas? or ?
It's a command handling issue (figuring out why the commands are disabled when they should be enabled). Who owns command handling for composer these days? Whether it should work in textareas in general is another issue which UI people should decide (so that should be made a separate bug which can be assigned to someone in a position to make that decision). In a browser window, if focus is in a textarea/text field would the user really want cmd-F to search only in the text control and not in the whole window? Though it might be that turning it on for the plaintext editor would also turn it on for text controls. Charley might know.
I filed bug 120568 about implementing find/change for text fields in the browser.
*** Bug 120568 has been marked as a duplicate of this bug. ***
*** Bug 121988 has been marked as a duplicate of this bug. ***
*** Bug 114829 has been marked as a duplicate of this bug. ***
*** Bug 127643 has been marked as a duplicate of this bug. ***
*** Bug 131433 has been marked as a duplicate of this bug. ***
*** Bug 132998 has been marked as a duplicate of this bug. ***
More to it than simply a capability that got disabled somehow. I realize the thing about a "boring consistancy," but -- The Browser has a MENU=[Search][Find] The MailNews has a MENU=[Search][Find] It violates the "Principle of Least Surprise" to find that the Composer does not have a MENU=[Search] but locates the [Find] function under MENU=[Edit]. Of course ViewSource also locates it under MENU=[Edit]! Is consistancy too much to expect?
Is the target for this bug still 1.0.1? Just wondering if that is makeable, or if it should be delayed?
*** Bug 144111 has been marked as a duplicate of this bug. ***
*** Bug 148340 has been marked as a duplicate of this bug. ***
*** Bug 151926 has been marked as a duplicate of this bug. ***
Priority: -- → P3
Target Milestone: mozilla1.0.1 → Future
*** Bug 157442 has been marked as a duplicate of this bug. ***
on Bug 157442 marked as duplicate of this, i said also that on My mac i don't see "find" or "replace" in the composer edit menu, source editing or not Command+F works (the dialog is opened) except for "view source" Build: 2002071303
*** Bug 161193 has been marked as a duplicate of this bug. ***
Find/Replace for textareas is covered by bug 120568.
Summary: No [Find] or [Replace] in HTML Source editor and other textareas → No [Find] or [Replace] in HTML Source editor
But the HTML Source window is simple a textarea. It doesn't matter if it's within the Composer app or in a web page. When bug 120568 is fixed, so will this. I feel like dupping this, but I'll add a dependency of now.
Depends on: 120568
*** Bug 164354 has been marked as a duplicate of this bug. ***
*** Bug 165165 has been marked as a duplicate of this bug. ***
*** Bug 168000 has been marked as a duplicate of this bug. ***
*** Bug 167950 has been marked as a duplicate of this bug. ***
*** Bug 169341 has been marked as a duplicate of this bug. ***
Keywords: mozilla1.1 → mozilla1.3
*** Bug 182439 has been marked as a duplicate of this bug. ***
*** Bug 188260 has been marked as a duplicate of this bug. ***
*** Bug 201913 has been marked as a duplicate of this bug. ***
Please add the words "Search" and "Composer" to the summary. It is almost impossible to find this bug (I actually managed to find it through one of the dupes). And while you're at it, feel free to mark Bug 195829 as another dupe... Prog.
QA Contact: sujay → sairuh
Summary: No [Find] or [Replace] in HTML Source editor → no [Find] or [Replace] in HTML source editor for Composer
*** Bug 195829 has been marked as a duplicate of this bug. ***
Summary: no [Find] or [Replace] in HTML source editor for Composer → no [Find] ([Search]) or [Replace] in HTML source editor for Composer
Shouldn't the lack of a search option in Composer's source pane be filed under Editor:Composer instead of Editor:Core? Prog.
fixed by bug 69329 :-) *** This bug has been marked as a duplicate of 69320 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Sorry, duped to wrong bug number. Need to sleep.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Really duping, sorry for spam. *** This bug has been marked as a duplicate of 69329 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.