1628412 - Find does not work in debugQA's text editor

Status: RESOLVED FIXED

(SeaMonkey :: Find In Page, defect)

Description

[Ian Neal]

If you select Edit->Find in debugQA's Text Editor nothing happens and you get some messages in the error console:
Timestamp: 4/8/20, 5:33:19 PM GMT+1
Error: TypeError: document.getElementById(...) is null
Source File: chrome://editor/content/ComposerCommands.js
Line: 2290
Timestamp: 4/8/20, 5:33:19 PM GMT+1
Error: An error occurred executing the cmd_find command: [Exception... "[JavaScript Error: "document.getElementById(...) is null" {file: "chrome://editor/content/ComposerCommands.js" line: 2290}]'[JavaScript Error: "document.getElementById(...) is null" {file: "chrome://editor/content/ComposerCommands.js" line: 2290}]' when calling method: [nsIControllerCommand::doCommand]" nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)" location: "JS frame :: chrome://global/content/globalOverlay.js :: goDoCommand :: line 93" data: yes]
Source File: chrome://global/content/globalOverlay.js
Line: 95

Comment 1

[Ian Neal]

Attachment: Fix find in Text Editor

[Approval Request Comment]
Regression caused by (bug #): unknown
User impact if declined: cannot use find in text editor
Testing completed (on m-c, etc.): 2.53
Risk to taking this patch (and alternatives if risky): none
String changes made by this patch: none

Comment 2

[Frank-Rainer Grahl (:frg)]

Comment on attachment 9139227 [details] [diff] [review]
Fix find in Text Editor

LGTM

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/comm-central/rev/e7b674413abc
Find does not work in debugQA's text editor. r=frg DONTBUILD