What needs to be done for Jetpack to support Firebug?
Steven Roussey
Brian King
> What needs to be done for Jetpack to support Firebug?
In the Develop section of about:jetpack, you'll see:
You either don't have the latest version of Firebug installed, or you
don't have it enabled for this page, so all logging messages will appear
in the JS Error Console. If you get Firebug 1.4 Alpha and enable it for
this page, and then reload this page, all logging messages will be
logged to the Firebug Console, where it's much easier to debug problems
and inspect live objects.
Could you be more specific about what you are looking for?
--
Brian King
BRIKS Software - http://briks.si
Mozilla Development Services
Twitter: http://twitter.com/brianking
Hernan Rodriguez Colmeiro
>
> Steven Roussey wrote:
>> What needs to be done for Jetpack to support Firebug?
>
> In the Develop section of about:jetpack, you'll see:
>
> You either don't have the latest version of Firebug installed, or you
> don't have it enabled for this page, so all logging messages will appear
> in the JS Error Console. If you get Firebug 1.4 Alpha and enable it for
> this page, and then reload this page, all logging messages will be
> logged to the Firebug Console, where it's much easier to debug problems
> and inspect live objects.
>
Steven and I participate actively in firebug development, and we think
that this issue could be most on the Firebug side.
Since Firebug 1.4.3, firebug doesn't stay on for internal pages like
"about:*". I think this was a fix regarding a bug in where Firebug
automatically opened in every about:* page, and indirectly we rendered
Firebug somewhat useless for Jetpack development.
A bug has been opened in firebug to handle this situation and quickly
fix it, feel free to add any input you may have:
http://code.google.com/p/fbug/issues/detail?id=2473
As a side note, I asked this on the IRC channel, but had no answer:
Why is Jetpack only capable to log to the Firebug console (assuming
you're using Firebug 1.4.2, where everything worked OK) in the
about:jetpack "page"?
Hernán Rodríguez Colmeiro
Honza (Jan Odvarko)
> fix it, feel free to add any input you may have:
>
> http://code.google.com/p/fbug/issues/detail?id=2473
APIs from Firebug 1.4, Firebug.URLSelector has been replaced by
Firebug.Activation (in 1.4.3)
The code should look like as follows:
var JetpackTabWatcher = {
shouldCreateContext: function(browser, uri) {
if (uri == JETPACK_URL) {
Firebug.Activation.watchBrowser(browser);
return true;
}
},
Honza
Honza (Jan Odvarko)
Matěj Cepl
To make it clear I have created a repo with this patch
(http://repo.or.cz/w/jetpack.git/tree/firebug-bug527647) and it seems to
work pretty well with precompiled components on my Fedora Rawhide
x86_64. When running tests the only one which fails is
SecureMembraneTests.testSecureMembraneQueryInterface which fails with:
Error: [Exception... "Could not convert JavaScript argument arg 0
[nsISupports.QueryInterface]" nsresult: "0x80570009
(NS_ERROR_XPC_BAD_CONVERT_JS)" location: "JS frame ::
chrome://jetpack/content/js/secure-membrane.js :: call :: line 285"
data: no]
Source file: chrome://jetpack/content/js/secure-membrane.js
Line: 285
However, console.log still points to the Javascript Error Console.
What's wrong with me?
Matěj
--
http://www.ceplovi.cz/matej/, Jabber: mcepl<at>ceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC
Whenever Christ our life is revealed, then also you will be
revealed with Him in glory.
-- Colossians 3:4 (Green's Literal Translation)
