1159100 - Debug Plaintext editor is broken from charsetOverlay no element found

Status: RESOLVED INVALID

(SeaMonkey :: Composer, defect)

Description

[Ian Neal]

Using a current trunk build
STR
1. Open Composer
2. Open Error Console and clear
3. Go to debug menu and select Plaintext Editor

Expected result
1. Editor opens correctly and no fatal errors

Actual result
1. Editor opens with missing bars/icons
2. Error Console contains the following errors:
Timestamp: 27/04/15 23:18:23
Error: no element found
Source File: chrome://global/content/charsetOverlay.xul
Line: 1
Timestamp: 27/04/15 23:18:23
Error: TypeError: insertBefore is null
Source File: chrome://communicator/content/viewZoomOverlay.js
Line: 350
Timestamp: 27/04/15 23:18:23
Error: ReferenceError: InlineSpellCheckerUI is not defined
Source File: chrome://editor/content/editor.js
Line: 289

The first error is probably the most important. Not sure how it is picking up that URL as all references in mxr seem to be for chrome://communicator/content/charsetOverlay.xul not chrome://global/content/charsetOverlay.xul

Comment 1

[Ian Neal]

Any idea how it is picking up the wrong URL?

Comment 2

[[e-mail]]

Out of interest, I tried on a build from 27th March and got the following exception:
Error: TypeError: redeclaration of const webPersist
Source File: chrome://editor/content/ComposerCommands.js
Line: 881
const webPersist = Components.interfaces.nsIWebBrowserPersist;

Comment 3

[[e-mail]]

My build from 4 days ago still only has the redeclaration error.

(I did notice a FullZoom error when closing Composer, and Find doesn't work, although Find and Replace does.)

Comment 4

[Ian Neal]

Looks like it is profile related, as a new profile works fine. Is there anything cached that would have a reference to the old charsetOverlay.xul URL?

Comment 5

[Philip Chee]

I just did a build an hour ago. Works for me.
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0 SeaMonkey/2.37a1
Build identifier: 20150428230929

Comment 6

[Ian Neal]

I build with lightning enabled so maybe an old version of that extension was causing the problem (even though it was disabled).