It may feel nasty if some people (like me) keep on insisting on the
midas-bug, but I'll take that risk...

I built the trunk-Camino with debug flags, and fired it onto
http://www.mozilla.org/editor/midasdemo/

Maybe some developer already saw this.
in this case I apologize for "spamming".

Otherwise, maybe it can help for a first glance at it...
as expected from the visible behavior, Camino seems unable to
enable the "designMode" on the iFrame supposed to contain the editable
area.

Here's what I see in the console.log when loading the page.

------- from console.log: -------

###!!! ASSERTION: should have been able to get the editing session here: 'editingSession', file nsDocShellEditorData.cpp, line 255
Break: at file nsDocShellEditorData.cpp, line 255
###!!! ASSERTION: nsFrameManager::GenerateStateKey didn't find content by type! See bug 139568: 'index > -1', file nsContentUtils.cpp, line 1466
Break: at file nsContentUtils.cpp, line 1466
###!!! ASSERTION: nsFrameManager::GenerateStateKey didn't find content by type! See bug 139568: 'index > -1', file nsContentUtils.cpp, line 1466
Break: at file nsContentUtils.cpp, line 1466
###!!! ASSERTION: nsFrameManager::GenerateStateKey didn't find content by type! See bug 139568: 'index > -1', file nsContentUtils.cpp, line 1466
Break: at file nsContentUtils.cpp, line 1466
++WEBSHELL == 4
++DOMWINDOW == 4
++WEBSHELL == 5
++DOMWINDOW == 5
--WEBSHELL == 4
--WEBSHELL == 3
###!!! ASSERTION: should have been able to get the editing session here: 'editingSession', file nsDocShellEditorData.cpp, line 255
Break: at file nsDocShellEditorData.cpp, line 255
JavaScript error: , line 0: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLDocument.designMode]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: http://www.mozilla.org/editor/midasdemo/ :: Start :: line 221" data: no]
2004-06-02 01:11:55.034 Camino[3408] JS error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLDocument.designMode]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: http://www.mozilla.org/editor/midasdemo/ :: Start :: line 221" data: no]


----------------------------------

On an implementation of itools-htmlarea, I did not get so many warnings, instead just

------- from console.log: -------

++WEBSHELL == 7
++DOMWINDOW == 7

###!!! ASSERTION: should have been able to get the editing session here: 'editingSession', file nsDocShellEditorData.cpp, line 255

Break: at file nsDocShellEditorData.cpp, line 255

JavaScript error: , line 0: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLDocument.designMode]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: http://testsite.intranet/javascripts/htmlarea/htmlarea.js :: initIframe :: line 748" data: no]

2004-06-02 01:00:04.168 Camino[3366] JS error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLDocument.designMode]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: http://testsite.intranet/javascripts/htmlarea/htmlarea.js :: initIframe :: line 748" data: no]


----- a snippet of the code referred to in the error: ---- (mozilla/docshell/base/nsDocShellEditorData.cpp, lines 248-257)

else
{
// otherwise we're on a subshell. In this case, call GetInterface
// on the root shell, which will come back into this routine,
// to the block above, and give us back the editing session on
// the content root.
nsCOMPtr<nsIEditingSession> editingSession = do_GetInterface(contentRootShell);
NS_ASSERTION(editingSession, "should have been able to get the editing session here");
NS_IF_ADDREF(*outEditingSession = editingSession.get());
}


thanx for listening,

regards,
Lorenzo


On 27. Mai 2004, at 6:23, Stuart Morgan wrote:

On May 26, 2004, at 11:36 PM, ludovic Hirlimann wrote:

Asaf Romano wrote:

BTW build extesions, what about including the midas extension in Camino?
Is there a chance to combain it in before 0.8f?


Bug # ? I don't think so

It's bug 197253. Given that there's no patch for it and no-one appears to be working on it, the chances of it making 0.8 are pretty much nil (unless someone steps forward to do it, and it's easy).


-Stuart Morgan

_______________________________________________
Camino mailing list
[EMAIL PROTECTED]
http://mozdev.org/mailman/listinfo/camino

_______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino

Reply via email to