Re: TB-3.0a1pre.en-US.win32.installer.exe + debugger
gNeandr <neandrNEWS@no_SP_AM_gmx.de> Fri, 09 May 2008 15:45:49 +0200
| Newsgroups | gmane.comp.mozilla.devel.jsdebugger |
|---|---|
| Message-ID | <[email protected]> |
On 05.05.2008 16:18 » Gijs Kruitbosch« wrote: > gNeandr wrote: >> On 05.05.2008 16:00 » Gijs Kruitbosch« wrote: >> > https://bugzilla.mozilla.org/show_bug.cgi?id=428848 >>> >>> Find the relevant chrome.manifest file that should have been created >>> in your profile, add " contentaccessible=yes" to the relevant lines, >>> and you should be fine. >>> >>> ~ Gijs >> Thanks Gijs for your prompt answer. >> >> Sorry, but do you tell me just to add a line "contentaccessible=yes" >> to the file? I can't believe that's true. >> You speak about "relevant lines". .. Please get it named completly for >> me. >> The file right now is: >> overlay chrome://communicator/content/tasksOverlay.xul >> chrome://venkman/content/venkman-overlay.xul >> overlay chrome://browser/content/browser.xul >> chrome://venkman/content/venkman-overlay.xul >> overlay chrome://messenger/content/messenger.xul >> chrome://venkman/content/venkman-overlay.xul >> overlay chrome://calendar/content/calendar.xul >> chrome://venkman/content/venkman-overlay.xul >> content venkman jar:chrome/venkman.jar!/content/venkman/ >> >> content venkman-ff jar:chrome/venkman.jar!/content/venkman/ff/ >> >> skin venkman modern/1.0 jar:chrome/venkman.jar!/skin/modern/venkman/ >> style chrome://global/content/customizeToolbar.xul >> chrome://venkman/skin/venkman-overlay.css >> >> locale venkman en-US jar:chrome/venkman.jar!/locale/en-US/venkman/ > > For this particular error: > > skin venkman modern/1.0 jar:chrome/venkman.jar!/skin/modern/venkman/ > contentaccessible=yes > > (you might find the line wrapped on the news server - it should all be > on one line) > > If that doesn't help, apply the same fix to the lines starting "content". > > ~ Gijs Hi Gijs, after some testing and checking with "http://developer.mozilla.org/en/docs/Chrome_Registration" now I have it running. From that page I understand the addition "contentaccessible=yes" has to added only to lines starting with "content". Doing so, it seems to run now! But I have a new error at startup of Venkman: Fehler: [Exception... "Component returned failure code: 0x80570018 (NS_ERROR_XPC_BAD_IID) [nsIJSCID.createInstance]" nsresult: "0x80570018 (NS_ERROR_XPC_BAD_IID)" location: "JS frame :: chrome://global/content/bindings/browser.xml :: :: line 644" data: no] Quelldatei: chrome://global/content/bindings/browser.xml Zeile: 650 Günter