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 > > On Tue, Feb 17, 2009 at 11:21 PM, Geuis <geuis.te...@gmail.com> wrote: > > > I get this error in Firebug quite often and it never seems to be > > related to any of my code in a page. Has anyone ever tracked down what > > causes this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to firebug@googlegroups.com To unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
