Open Bug 488745 Opened 16 years ago Updated 15 years ago

mochitest-chrome 'test_idcheck.xul > editor.xul' reports 2 "Error: GetCurrentCommandManager is not defined" in editor.js

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: sgautherie, Unassigned)

References

()

Details

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.2a1pre) Gecko/20090410 SeaMonkey/2.0b1pre] (experimental/_m-c_, home, optim default) (W2Ksp4) (http://hg.mozilla.org/mozilla-central/rev/1a8349d0cff8 +http://hg.mozilla.org/comm-central/rev/671042296bda) { Error: GetCurrentCommandManager is not defined Source File: chrome://editor/content/editor.js Line: 340 }
Summary: mochitest-chrome test_idcheck.xul reports 2 "Error: GetCurrentCommandManager is not defined" in editor.js → mochitest-chrome 'test_idcheck.xul > editor.xul' reports 2 "Error: GetCurrentCommandManager is not defined" in editor.js
Tough the includes seem correct: editor.xul <-- editorOverlay.xul <-- editorUtilities.js
Or could this editor.js code be run before the overlay is (fully) processed?
Depends on: 502603
No longer depends on: 481406
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.3a1pre) Gecko/20100131 SeaMonkey/2.1a1pre] (home, optim default) (W2Ksp4) (Bug still there.)
You need to log in before you can comment on or make changes to this bug.