Steps: 1. File>Open [Address] 2. Enter a path to a file that doesn't exist 3. Select open in composer 4. click open. Expected, as seen using > notepad nonexistantfile Notepad Cannot find the fi.txt file. Do you want to create a new file? Yes No Win98 Composer HTML Editor opens w/ uneditable view. Various errors can be triggered while trying to 'use' the editor. -- No changes are possible... Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIEditorShell.LoadUrl]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://editor/content/editor.js :: EditorStartup :: line 246" data: no] Error: uncaught exception: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIEditorShell.editorDocument]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: chrome://editor/content/editor.js :: SetEditMode :: line 1130" data: no] Error: uncaught exception: [Exception... "Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIEditorShell.GetTextProperty]" nsresult: "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: chrome://editor/content/editor.js :: initFontFaceMenu :: line 721" data: no] This is probably related to Bug 93475 however the suggested fix there won't work here (and the underlying problem which should probably be fixed here so that the editor will function at all...) I'm about to file a similar bug for FreeBSD, however the behavior is significantly different.
Assignee: syd → brade
timeless--you could fix this bug if you wanted ;-)
Target Milestone: mozilla1.0.1 → mozilla1.2alpha
Is this still a bug? If so, can you provide more updated debug info? (editorShell is now gone)
Error ``GetCurrentEditor() has no properties'' [xs] in file ``chrome://editor/content/editorUtilities.js'', line 825, character 0. Stopped for error handler. #0: function GetDocumentUrl() in <chrome://editor/content/editorUtilities.js> line 825
Assignee: brade → nobody
QA Contact: sujay → composer
Target Milestone: Future → ---
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.