CSSUpdater

278 views
Skip to first unread message

nero

unread,
Sep 25, 2011, 6:48:21 AM9/25/11
to Firebug
http://cssupdater.com/

Cool little Adobe Air/FF extensión coupling that worked fine for me
but no longer functions in 1.9.

How can I help in finding out where the breakage is happening?

Jan Honza Odvarko

unread,
Sep 26, 2011, 9:19:31 AM9/26/11
to Firebug
Install FBTrace (Firebug tracing console) together with Firebug and
the extension:
http://getfirebug.com/releases/firebug/1.9/firebug-1.9.0a3.xpi
http://getfirebug.com/releases/fbtrace/1.9/fbTrace-1.9b2.xpi

More about FBTrace:
http://getfirebug.com/wiki/index.php/FBTrace

First check ERRORS options (in the tracing console)
and check whether there are any errors.

You can also utilize the Firefox Error Console
(but FBTrace shows more)

Honza

Nero

unread,
Sep 26, 2011, 11:00:50 AM9/26/11
to fir...@googlegroups.com
Hi Honza,

It's showing that the extension is installed but when I make changes to the CSS via firebug I don't see any errors which I'm guessing means that while the extension is installed in Firefox correctly that it's not connected to FB at all.

5

makeURI FAILS for "chrome://mozapps" Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIIOService.newURI]
resource://firebug_rjs/lib/url.js (517) [...]
resource://firebug_rjs/chrome/activation.js (210) [...]
resource://firebug_rjs/chrome/activation.js (81) [...]
resource://firebug_rjs/lib/events.js (105) [...]
resource://firebug_rjs/bti/inProcess/browser.js (764) [...]
resource://firebug_rjs/lib/events.js (105) [...]
resource://firebug_rjs/firefox/tabWatcher.js (301) [...]
resource://firebug_rjs/firefox/tabWatcher.js (162) [...]
resource://firebug_rjs/firefox/tabWatcher.js (780) [...]
chrome://browser/content/tabbrowser.xml (410) [...]
chrome://browser/content/tabbrowser.xml (407) [...]
chrome://tabutils/content/tulib.js (100) [...]
chrome://tabutils/content/tulib.js (105) [...]
resource:///components/nsSessionStore.js (2848) [...]
resource:///components/nsSessionStore.js (2684) [...]
resource:///components/nsSessionStore.js (806) [...]
resource:///components/nsSessionStore.js (423) [...]
chrome://browser/content/browser.js (7563) [...]
 () [...]

6

makeURI FAILS for "chrome://mozapps" Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIIOService.newURI]
resource://firebug_rjs/lib/url.js (517) [...]
resource://firebug_rjs/chrome/activation.js (210) [...]
resource://firebug_rjs/chrome/activation.js (81) [...]
resource://firebug_rjs/lib/events.js (105) [...]
resource://firebug_rjs/firefox/tabWatcher.js (301) [...]
resource://firebug_rjs/firefox/tabWatcher.js (162) [...]
resource://firebug_rjs/firefox/tabWatcher.js (780) [...]
chrome://browser/content/tabbrowser.xml (410) [...]
chrome://browser/content/tabbrowser.xml (407) [...]
chrome://tabutils/content/tulib.js (100) [...]
chrome://tabutils/content/tulib.js (105) [...]
resource:///components/nsSessionStore.js (2848) [...]
resource:///components/nsSessionStore.js (2684) [...]
resource:///components/nsSessionStore.js (806) [...]
resource:///components/nsSessionStore.js (423) [...]
chrome://browser/content/browser.js (7563) [...]
 () [...]

7
makeURI FAILS for "chrome://mozapps" Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIIOService.newURI]
8
makeURI FAILS for "chrome://mozapps" Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIIOService.newURI]


Are there any other options in Trace that I should be activating?



--
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 http://groups.google.com/group/firebug?hl=en.


Jan Honza Odvarko

unread,
Sep 26, 2011, 11:24:51 AM9/26/11
to Firebug
On Sep 26, 5:00 pm, Nero <ner...@gmail.com> wrote:
> Are there any other options in Trace that I should be activating?
Yes, the Console has three tabs: Logs, Options and Global Events.

Go to Options and check e.g. ERRORS

You can check other options too, but be careful some of them generate
a lot of logs.

Honza

Nero

unread,
Sep 26, 2011, 11:28:25 AM9/26/11
to fir...@googlegroups.com
Errors is the only one that I have checked and still nothing showed up.  Am I to assume that in this case it's the extension itself that needs fixing and nothing something in Firebug?

Is there any info I can forward along to the developer?


--

Jan Honza Odvarko

unread,
Sep 27, 2011, 6:02:15 AM9/27/11
to Firebug
On Sep 26, 5:28 pm, Nero <ner...@gmail.com> wrote:
> Errors is the only one that I have checked and still nothing showed up.  Am
> I to assume that in this case it's the extension itself that needs fixing
> and nothing something in Firebug?
The Firefox Error console also doesn't show any error/exception?

> Is there any info I can forward along to the developer?
The most important info for a developer is usually a test case
+ detailed steps how to reproduce the problem.

I don't know how long the extension wasn't updated, but
sometime along Firebug 1.7 release we removed two global
variables:

FirebugContext -> is now -> Firebug.currentContext
FirebugChrome -> is now -> Firebug.chrome

You could also mention this to the developer
Honza

Jhonte

unread,
Sep 27, 2011, 2:18:53 PM9/27/11
to fir...@googlegroups.com
Thanks for trying to help Nero :)

The global variable thing is check, however it seems like the whole setup part has changed.
Where can I find some information about this?

I'm talking about the:
FBL.ns(function() { with (FBL) {

Google couldn't help me :(


Jhonte

unread,
Sep 27, 2011, 1:53:39 PM9/27/11
to Firebug
Thank you for trying to help Nero :)

The global variables is check, how ever it seems like this code:
FBL.ns(function() { with (FBL) {

Should be something totally different in 1.9? Where can I find
documentation about this change, (and how can I make it work with
FireBug < 1.9)

Jan Honza Odvarko

unread,
Sep 29, 2011, 9:47:30 AM9/29/11
to Firebug
Take a look at this HelloWorld example:
http://code.google.com/p/fbug/source/browse/#svn%2Fexamples%2Ffirebug1.9%2FHelloWorld

It works for me in Firebug 1.8 and 1.9

It also uses the same boilerplate:

FBL.ns(function() { with (FBL) {


Honza

Johan Andersson

unread,
Sep 30, 2011, 4:56:48 PM9/30/11
to fir...@googlegroups.com
Thank you for answering!

But I can't see anything special with your example that I isn't doing.
The only diff I see is that I use ActivablePanel and module.

So when I add this fail safe debug logic (without anything in the middle)

alert("first line");
FBL.ns(function() { with (FBL) {
alert("middle line");
}});
alert("last line");

Then the first and last line is alerted. It does not even try to execute the thing in between for me.
Using FireBug 1.9.0a3, FireFox 6.0.2

Jan Honza Odvarko

unread,
Oct 1, 2011, 8:16:16 AM10/1/11
to Firebug
Please send me the entire extension I'll take a look at it on my
machine.

Honza

On Sep 30, 10:56 pm, Johan Andersson <johan.anderss...@gmail.com>
wrote:
> Thank you for answering!
>
> But I can't see anything special with your example that I isn't doing.
> The only diff I see is that I use ActivablePanel and module.
>
> So when I add this fail safe debug logic (without anything in the middle)
>
> alert("first line");
> FBL.ns(function() { with (FBL) {
>         alert("middle line");}});
>
> alert("last line");
>
> Then the first and last line is alerted.    It does not even try to execute the thing in between for me.
> Using FireBug 1.9.0a3,  FireFox 6.0.2
>
> On Sep 29, 2011, at 3:47 PM, Jan Honza Odvarko wrote:
>
>
>
>
>
>
>
> > Take a look at this HelloWorld example:
> >http://code.google.com/p/fbug/source/browse/#svn%2Fexamples%2Ffirebug...

Jan Honza Odvarko

unread,
Oct 1, 2011, 8:49:22 AM10/1/11
to Firebug
You need to overlay firebugOverlay.xul in your chrome.manifest file:

overlay chrome://firebug/content/firebugOverlay.xul
chrome://cssUpdater/content/ff-overlay.xul

(not browser.xul)

When I change that the extension seems to be working again.

Honza


On Sep 30, 10:56 pm, Johan Andersson <johan.anderss...@gmail.com>
wrote:
> Thank you for answering!
>
> But I can't see anything special with your example that I isn't doing.
> The only diff I see is that I use ActivablePanel and module.
>
> So when I add this fail safe debug logic (without anything in the middle)
>
> alert("first line");
> FBL.ns(function() { with (FBL) {
>         alert("middle line");}});
>
> alert("last line");
>
> Then the first and last line is alerted.    It does not even try to execute the thing in between for me.
> Using FireBug 1.9.0a3,  FireFox 6.0.2
>
> On Sep 29, 2011, at 3:47 PM, Jan Honza Odvarko wrote:
>
>
>
>
>
>
>
> > Take a look at this HelloWorld example:
> >http://code.google.com/p/fbug/source/browse/#svn%2Fexamples%2Ffirebug...

Johan Andersson

unread,
Oct 1, 2011, 9:13:48 AM10/1/11
to fir...@googlegroups.com
+1 on that!

THANK YOU!

Reply all
Reply to author
Forward
0 new messages