console.* Failing - Firefox 14.0.1, Firebug >1.9.2

207 views
Skip to first unread message

Lucanos

unread,
Aug 21, 2012, 2:24:48 PM8/21/12
to fir...@googlegroups.com
I am unable to get any of the console.* functions ( ie console.log(...) ) to work at all within Firefox v14.0.1 when using any version of Firebug greater than v1.9.2

I have disabled all other extensions and retested - same results.
I have even tried using Firebug v1.11.0a1 - same results.

Jan Honza Odvarko

unread,
Aug 21, 2012, 2:26:33 PM8/21/12
to Firebug
Did you try a new Firefox profile?
http://getfirebug.com/wiki/index.php/FAQ#Installing_in_a_clean_profile

Honza

On Aug 21, 8:24 pm, Lucanos <luca...@gmail.com> wrote:
> I am unable to get any of the console.* functions ( ie *console.log(...)* )

Sebastian Zartner

unread,
Aug 21, 2012, 5:49:39 PM8/21/12
to fir...@googlegroups.com
Also note that Firebug doesn't overwrite an existing console object, i.e. if the JavaScript inside your page defines e.g. var console = 1;, then the console API won't be available.

Sebastian

Jan Honza Odvarko

unread,
Aug 23, 2012, 9:44:31 AM8/23/12
to Firebug
Yes, I got it, sorry it's still in my TODO queue... :-)

Honza

On Aug 23, 3:37 pm, fusionX <dantz...@gmail.com> wrote:
> Hello Odvarko
>
> I sent you an email response, can you confirm?
>
> And that you might be able to help or what your thoughts are please. There
> is no real rush, i just wan to make sure hands are on it.
>
> thank you
> Don

Sebastian Zartner

unread,
Aug 23, 2012, 9:52:19 AM8/23/12
to fir...@googlegroups.com
What did you send Honza? If it's a test case showing that the console.* functions are not working, you may want to post it publicly, so others can also reproduce it.

Sebastian

Don Antz

unread,
Aug 23, 2012, 6:31:05 PM8/23/12
to fir...@googlegroups.com
Sorry it is nothing special, just a small TO-DO list for Honza. I know your busy, and appreciate your time, I eagerly await your findings and I am hopeful this is achieveable via Firebug or script etc.
 
Let me saySebastian, Firebug rocks doesnt it.
 
Honaza, truely optimistic here bud...I will be here when you reach back to me.
 
cheers

--
You received this message because you are subscribed to the Google
Groups "Firebug" group.
To post to this group, send email to fir...@googlegroups.com
To unsubscribe from this group, send email to
firebug+u...@googlegroups.com
For more options, visit this group at
https://groups.google.com/forum/#!forum/firebug

Lucanos

unread,
Aug 26, 2012, 10:02:41 AM8/26/12
to fir...@googlegroups.com
Hi Honza,

Creating a new Profile does resolve the problem.
Of course, it replaces the "My Firebug doesn't work" problem with the "I have to reconfigure Firefox all over again" problem, which seems even larger.

It would be nice to actually know the cause of the problem, rather than applying this rather drastic fix.

Luke

Lucanos

unread,
Aug 26, 2012, 10:04:02 AM8/26/12
to fir...@googlegroups.com
Of course.
But the testing I did would have revealed that - same page, same javascript console commands, v1.10 fails to show anything, v1.9.2 shows the messages.
If the variable was being overwritten by the page, all versions would have experienced the problem.

Jan Honza Odvarko

unread,
Aug 26, 2012, 10:29:52 AM8/26/12
to Firebug
On Aug 26, 4:02 pm, Lucanos <luca...@gmail.com> wrote:
> Hi Honza,
>
> Creating a new Profile does resolve the problem.
> Of course, it replaces the "My Firebug doesn't work" problem with the "I
> have to reconfigure Firefox all over again" problem, which seems even
> larger.
>
> It would be nice to actually know the cause of the problem, rather than
> applying this rather drastic fix.
You can try to compare the two profiles and check out the differences.
E.g. the prefs.js (all preference settings) diff could be interesting.

You can also try to disable extension step by step and see if there
are any collisions...

Honza
Reply all
Reply to author
Forward
0 new messages