Is the Firebug console.log error fixed?

[Emre Sevinc]

Hello,

I'm using Firefox 3.5.6 with JetPack 0.7 and Firebug 1.4.5 and I have
problems debugging my jetpack application when I visit web pages.

Previously (when I was running Jetpack 0.6.2 on firefox 3.5.6) I was
able to visit any web page turn on the Firebug, run my jetpack and see
the console log messages in the Firebug console as I was looking at
that
page. E.g. I was visiting a Newsweek web page, the Firebug was turned
on, I was running my Jetpack and could see the relevant log message
below that web page, in the Firebug console.

Now I have updated to JetPack 0.7 (Firefox version is the same) and
whenever I visit pages and try to run my jetpack I get nothing at the
console. To make things stranger when I visit about:jetpack page,
activate Firebug and reload the page and try to run my jetpack it
works on that page and prints some relevant log messages to the
console.

The situation is that I can debug my jetpack only for the
about:jetpack page, for other web pages I don't get any messages to
the Firebug console.

I have read some relevant Google Groups messages and it says the
problems are already fixed and should be avaliable with the latest
version of Jetpack, which is 0.7

Any ideas about my problem and potential solution?

[XuluWarrior]

I commented on this in
http://groups.google.com/group/mozilla-labs-jetpack/browse_thread/thread/9a5bde2f5264c78f/11314ce6c0c22f5d#11314ce6c0c22f5d

I haven't managed to get any version later than Firebug 1.4.0 to work
with Jetpack and so for now I'm sticking to using that.