In some cases this message can be related to event handlers running in
closed windows. So window A sets a callback on window B, then later
window A is closed (or reloaded or src= changed or...). When window B
calls A, the call goes through, but the global scope of A is broken.
And the location object has been erased so you get errors if you try
to print window.location (which firebug does a lot to to error
tracking).
So its possible that this is caused by FIrebug or anyone else.
jjb
On Feb 17, 11:38 pm, gabriel munteanu <
jajali...@gmail.com> wrote:
> i can say that i saw this too. the error was related to totally something
> else, solved that error in my code and Location.toString vanished.
> but very weird indeed.
>
> jgabios
>