what you are saying is not a Firebug problem but a memory address corruption
in JavaScript which is absolutely a monster, rather than a bug.
If you assign in scope a variable and you have not access to that scope (
eval("toString=somethingElse", jQuery) in some old firefox with scope access
) the problem should never exists.
Regards
On Sat, Aug 1, 2009 at 3:51 PM, lrbabe <lrb...@gmail.com> wrote:
>
> I personally would just recommend not to use:
> return toString.call(obj) === "[object Object]"
> like in isArray or isFunction but instead:
> return Object.prototype.toString.call(obj) === "[object Object]"
> or something else, because I've already seen the former yielding
> results like "[xpconnect native prototype wrapper]"
> It might be a Firebug bug, I'm not really sure, but using the
> Object.prototype prefix solved the problem.
>
> Regards,
> Louis-Rémi Babé
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
