I just finished doing that in a new profile and firebug was still
working. :/

My main profile has been in use for a long time and lived through a
lot of nightly and local builds, maybe it's time to start a new one.

>From what I could tell, the following expression was triggering the
Trace message (lib.js):

   set: function(name, value)  // value will be another toggle branch
    {
        if (FBTrace.DBG_DOMPLATE)
            if (value && !(value instanceof ToggleBranch))
FBTrace.sysout("ERROR ToggleBranch.set("+name+","+value+") not set to
a ToggleBranch!");


in chromeBug's Watch window everything seemed fine, though.


On Jan 17, 8:50 pm, Steven Roussey <srous...@gmail.com> wrote:
> > Couldn't reproduce these issues in a clean profile so it's definitely
> > extensions interfering.
>
> Could you iterate through the extensions (turn off half at a time to narrow
> down) and let us know?
>
> -steve--

-- 
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.

Reply via email to