[Mozile] mozile 0.8::Firebug incompatibility?

James A. Overton james at overton.ca
Fri May 5 11:42:38 EDT 2006


	Ok. Using an onload handler instead would be just fine. I did it the  
other way just to cut down on the number of lines of code. I can't  
see any disadvantages to using a handler.
	If you've got it working, send me the code and I'll integrate the fix.
	Thanks,

James


On 2006-May-05, at 10:10 AM, david wrote:

>>     The problem could be Mozile, but it's probably Firebug. They  
>> muck around with the XMLHttpRequest object in order to capture the  
>> data flowing through it, and it messes up the loading code in  
>> mozile.js.
>>     They'd probably appreciate it if you could create a minimal  
>> test case and post a bug report for it. On the other hand, nobody  
>> ever replied to my bug report... :^)
>
> Did some digging. It looks as a timing issue. If the calls to  
> mozile.loadCore and the loadModule() calls are made in an onload  
> handler, firebug does not complain (and mozile seem to work fine  
> too actually). If the calls are made from the root scope, the error  
> is back. It does not matter if the mozile object is involved.
>
> In other words: Firebug does not like XMLHttpRequests made from the  
> root scope (not even switching from syncronous calls to asyncronous  
> ones).
>
> -- 
> "Notre malheur n'atteint son plus haut point que lorsque a été  
> envisagée, suffisamment proche, la possibilité pratique du bonheur."
> _______________________________________________
> Mozile mailing list
> Mozile at mozdev.org
> http://mozdev.org/mailman/listinfo/mozile



More information about the Mozile mailing list