My favorites | Sign in
Logo
             
New issue | Search
for
| Advanced search | Search tips
Issue 2473: Latest Firebug versions not activating in Jetpack Development page
1 person starred this issue and may be notified of changes. Back to list
Status:  OtherComponent
Owner:  odvarko
Closed:  Nov 10
1.4
Type-Defect
jetpack
bugzilla


Sign in to add a comment
 
Reported by colme...@gmail.com, Nov 09, 2009
What steps will reproduce the problem?
0. With any firebug newer than 1.4.2, try the following
1. Install Jetpack (https://jetpack.mozillalabs.com/install.html)
2. Go to about:jetpack
3. Go to "Tutorial" tab
4. In the Chapter 1 section, go for the third example, this is the one that
interacts with firebug
5. Click on the code, the jetpack should get temporarily installed (A
"Boom!" text should appear in the status bar).
6. Activate Firebug
7. Click on the "Boom!" Text


What is the expected result? What do you see instead?

The expected result is that the current jetpack.tabs object to be logged
into firebug's console. jetpack.tabs is the collection of the opened tabs,
to which jetpack has access.

What I see is nothing logged, instead of going to the firebug's console,
all the logging goes to the Firefox Error Console.

Which version of Firebug? (more specific than latest please):

With any Firebug version newer than 1.4.2

Which version of Firefox?
Reproduced in 3.5.4 & 3.5.5 (although this is not important, I think)

On what operating system?
Reproduced on Linux and Windows

I think that somewhere between the 1.4.2 and 1.4.3 an issue regarding the
"about:" pages was fixed so that firebug didn't enabled in any webpage
starting with "about:". In jetpack, all the logging is done exclusively
through "about:jetpack". 

You have to switch to that tab to see the logging, but since firebug doesnt
enable in those pages, jetpack doesn't see the console object. Sure you can
enable firebug once you loaded the page, but then is too late for Jetpack
to have it in it's scope I think.

So maybe doing some exception just for about:jetpack so that Firebug could
be enabled there may easily fix this.

HernĂ¡n
Comment 1 by odvarko, Nov 09, 2009
More info:
http://groups.google.com/group/mozilla-labs-jetpack/browse_thread/thread/fa1fe8462bc6093

Cc: odvarko
Labels: 1.4 Type-Defect jetpack
Comment 2 by odvarko, Nov 09, 2009
The problem is in firebug-extension.js, the JetpackTabWatcher uses old 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;
          }
        },

Comment 3 by odvarko, Nov 10, 2009
https://bugzilla.mozilla.org/show_bug.cgi?id=527647

Status: Triaged
Owner: odvarko
Cc: -odvarko
Labels: bugzilla
Comment 4 by johnjbar...@johnjbarton.com, Nov 10, 2009
Shouldn't this be closed on "OtherComponent"?
Comment 5 by odvarko, Nov 10, 2009
Yes, I am closing this one.
Honza
Status: OtherComponent
Sign in to add a comment

Hosted by Google Code