I, for one, am really glad to hear that you're working on performance
and stability. I know Firebug is better suited to being used in a
dedicated developer profile, but I relish the thought that I might be
able to keep Firebug on my day to day profile without a performance
penalty.
Previously, I used to disable Firebug when I wasn't specifically using
it, but I found that I missed it too much. It's nice to have it
available when you see something interesting on the web and you want
to find out how it works.
Can I post a little issue? It's with the website.. on the downloads page ( http://getfirebug.com/downloads ) the link for 1.8 points to the 1.7 release.
I was looking for an email address to report this issue to, I hope you don't mind me posting it here.
On Jul 30, 3:45 pm, "monk (freakyfractal)" <freakyfrac...@gmail.com>
wrote:
> Can I post a little issue? It's with the website.. on the downloads page (http://getfirebug.com/downloads) the link for 1.8 points to the 1.7
> release.
> I was looking for an email address to report this issue to, I hope you don't
> mind me posting it here.
On Aug 1, 8:43 pm, joelarson <joelars...@gmail.com> wrote:
> Brad - I have the same problem, and on the Customize screen I do not
> see a Firebug icon. Thoughts?
This could be a problem with the Firefox profile.
Please try following two things:
1) check out Firefox Error Console
Firefox Menu -> Web Developer -> Error Console
(or in Tools if you have traditional menu bar displayed)
Do you see any errors?
I installed a new profile and Firebug in this profile, but the Firebug
icon has not appeared, even after the Customize process (no Firebug
icon in the list).
On Aug 3, 10:04 am, Sullivan <s.gauvi...@gmail.com> wrote:
> Same problem here.
> I installed a new profile and Firebug in this profile, but the Firebug
> icon has not appeared, even after the Customize process (no Firebug
> icon in the list).
Do you have any other Firefox extension installed?
If you create a new Firefox profile (with only Firebug installed) does
it help?
i have the same problem with MacOSX ; Firefox 5.0.1.
I tried with a new profile and it works fine.
I tried disabling all my extensions and still won't work.
I have the followings errors in console :
Erreur : FBL.getAncestorByClass is not a function
Fichier Source : chrome://firebug/content/firefox/bindings.xml
Ligne : 443
Erreur : FBL.$STR is not a function
Fichier Source : chrome://firebug/content/firefox/bindings.xml
Ligne : 1391
Erreur : FBL.getAncestorByClass is not a function
Fichier Source : chrome://firebug/content/firefox/bindings.xml
Ligne : 443
Erreur : FBTrace is not installed, use empty implementation
Fichier Source : resource://firebug_rjs/lib/trace.js
Ligne : 16
My other extensions are : Colorzilla 2.5.5, FirefFTP 1.99.4, MeasureIt
0.4.9, Popup ALT Attribute 2.0.2011040501, ShowIP 1.0, Web Developer
1.1.9, Xmarks 4.0.1
I'm very disappointed by this new release of Firebug. I used to test
lot of code in the Javascript console, and Firebug always helped me to
find where my error was with a useful error message (where the syntax
error is or which one, etc). Now Firebug 1.8 returns a very useless
message that looks like Internet Explorer. Just a "syntax error", or
"type error" or just "error".....
Here is an example :
var foo = document.getElementById("something"); // with this id that
doesn't exist
foo=foo.parentNode;
Do I have to do anything special to have the previous clear and
helpful error message instead of this useless message ? If not, how
can I change the Firebug 1.7 to be compatible with Firefox 6 (I tried
to change install.rdf and zip again but Firefox doesn't want to
install it... maybe I should try to desactivate the compatibility in
Firefox directly :-/)
thanks for noticing this bug. it is caused by change in the way firefox nativeWrapers work firebug now doesn't understand that object is an error and just prints generic info will be fixed in the next release
On 19 août, 15:06, Harutyun Amirjanyan <amirjan...@gmail.com> wrote:
> thanks for noticing this bug.
> it is caused by change in the way firefox nativeWrapers work
> firebug now doesn't understand that object is an error and just prints
> generic info
> will be fixed in the next release