Re: TB-3.0a1pre.en-US.win32.installer.exe + debugger

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
Gijs it's a bit confusing!??

By "accident" I used my normal profile with TB3.0 [*] installation. That 
profile has the Venkman installed with normal chrome.manifest, saying it 
has none of the addition you described above ... and that configuration 
is running well!!

Starting TB3.0 and using a new profile it again shows a behavior as 
described before. Also those changes to the chrome.manifest didn't helped.

[*]  thunderbird-3.0a1.en-US.win32.installer.exe (as of 8. Mai 2008, 
09:45:00)