Boris Zbarsky wrote:
> John J. Barton wrote:
>> Just in case someone comes this way, the change that really bit me was
>> that window.location = "javascript:..." is now asynchronous. This
>> threw Firebug off
>
> Hmm. Are these javascript: URIs that you're loading, or that the page
> is loading? The impact of that change worries me, and I'd love any data
> on when and how it breaks existing expectations.
>
> -Boris
>
The code (in an extension of FF) is:
win.__firebugTemp__ = text;
win.location = "javascript: eval(__firebugTemp__);";
delete win.__firebugTemp__;
I have to say that I would have a hard time predicting what this is
supposed to do. What it did in FF2 was eval source in the context of the
window referenced by win. May still do that, but in FF3 the delete
erases the buffer before the eval() runs, and if I take out the delete,
then some other code relying on the eval() dies because the eval() runs
much later.
Joe Hewitt suggested looking at nsIXPCComponents_Utils evalInSandbox(),
but I've not tried it.
John.
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
