293362 - gSearchInput is not always defined in function Search

Status: RESOLVED FIXED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Ian Neal]

In some circumstances the following error message is generated in the JS console:
Error: gSearchInput has no properties
Source File: chrome://messenger/content/searchBar.js
Line: 527

Comment 1

[Ian Neal]

Attachment: Patch v0.1 (Checked in)

This patch:
* Moves GetSearchInput() to before the viewDebug command

Comment 2

[Ian Neal]

This patch actually fixes a problem with saved searches in that if you try and
view one as the first folder you are trying to view you just end up with a blank
thread pane. If you change to another folder and back again, the thread pane is
populated.
-> Normal

Comment 3

[Ian Neal]

Comment on attachment 182950 [details] [diff] [review]
Patch v0.1 (Checked in)

Requesting a= for very low risk suite only fix

Comment 4

[Mike Shaver (:shaver emeritus)]

Comment on attachment 182950 [details] [diff] [review]
Patch v0.1 (Checked in)

a=shaver

Comment 5

[Ian Neal]

Comment on attachment 182950 [details] [diff] [review]
Patch v0.1 (Checked in)

Checking in searchBar.js;
new revision: 1.41; previous revision: 1.40
done