I'm trying to use fb 1.2, since 1.1 gives the security error when
using the console. However, fb 1.2 does not work at all. On startup,
the first selected tab shows that it has N errors in the status bar
(even though fb is not even enabled, as the docs say that it is
disabled by default, and I perged the prefs.js related to firebug).
Pressing F12, or clicking on the bug icon, do not show the fb panel.
Nothing happens. Right clicking on the icon only has 'Clear console'
and 'open in new window'. Opening firebug in new window shows a messed-
up fb. The console has this message:
Firebug's log limit has been reached. %S entries not shown.
None of the styles are loaded, going to the HTML tab does not have any
images (like the '+' for the tree, etc). It uses the system style (in
my case, dark gray for the background), instead of white. Every tab
shows the above error, as well as any commands I've tried to run, like
'>>> 1'. The said commands do not do anything at all.
Started from the terminal, firefox has the following output:
> I'm trying to use fb 1.2, since 1.1 gives the security error when
> using the console. However, fb 1.2 does not work at all. On startup,
> the first selected tab shows that it has N errors in the status bar
> (even though fb is not even enabled, as the docs say that it is
> disabled by default, and I perged the prefs.js related to firebug).
> Pressing F12, or clicking on the bug icon, do not show the fb panel.
> Nothing happens. Right clicking on the icon only has 'Clear console'
> and 'open in new window'. Opening firebug in new window shows a messed-
> up fb. The console has this message:
> Firebug's log limit has been reached. %S entries not shown.
> None of the styles are loaded, going to the HTML tab does not have any
> images (like the '+' for the tree, etc). It uses the system style (in
> my case, dark gray for the background), instead of white. Every tab
> shows the above error, as well as any commands I've tried to run, like
> '>>> 1'. The said commands do not do anything at all.
> Started from the terminal, firefox has the following output:
> I'm getting the same problem using Ubuntu Hardy Heron and Firefox
> 3.0b5. Is there any way to solve it?
> On 18 abr, 10:45, Viktor Kojouharov <vkojouha...@gmail.com> wrote:
> > Hello,
> > I'm trying to use fb 1.2, since 1.1 gives the security error when
> > using the console. However, fb 1.2 does not work at all. On startup,
> > the first selected tab shows that it has N errors in the status bar
> > (even though fb is not even enabled, as the docs say that it is
> > disabled by default, and I perged the prefs.js related to firebug).
> > Pressing F12, or clicking on the bug icon, do not show the fb panel.
> > Nothing happens. Right clicking on the icon only has 'Clear console'
> > and 'open in new window'. Opening firebug in new window shows a messed-
> > up fb. The console has this message:
> > Firebug's log limit has been reached. %S entries not shown.
> > None of the styles are loaded, going to the HTML tab does not have any
> > images (like the '+' for the tree, etc). It uses the system style (in
> > my case, dark gray for the background), instead of white. Every tab
> > shows the above error, as well as any commands I've tried to run, like
> > '>>> 1'. The said commands do not do anything at all.
> > Started from the terminal, firefox has the following output:
On 18 apr, 13:39, Jan Odvarko <odva...@gmail.com> wrote:
> Have you tried to create a new fresh profile?
I'm having the same problem on my Hardy / FF 3b5 setup. I did try
moving my old profile out of the way. The only thing I have not yest
tried is removing the 'Ubuntu Firefox Modifications' extension that is
included in the Ubuntu package.
> Have you tried to create a new fresh profile?
> Honza
> On Apr 18, 11:59 am, Francisco <nfla...@gmail.com> wrote:
> > Hi,
> > I'm getting the same problem using Ubuntu Hardy Heron and Firefox
> > 3.0b5. Is there any way to solve it?
> > On 18 abr, 10:45, Viktor Kojouharov <vkojouha...@gmail.com> wrote:
> > > Hello,
> > > I'm trying to use fb 1.2, since 1.1 gives the security error when
> > > using the console. However, fb 1.2 does not work at all. On startup,
> > > the first selected tab shows that it has N errors in the status bar
> > > (even though fb is not even enabled, as the docs say that it is
> > > disabled by default, and I perged the prefs.js related to firebug).
> > > Pressing F12, or clicking on the bug icon, do not show the fb panel.
> > > Nothing happens. Right clicking on the icon only has 'Clear console'
> > > and 'open in new window'. Opening firebug in new window shows a messed-
> > > up fb. The console has this message:
> > > Firebug's log limit has been reached. %S entries not shown.
> > > None of the styles are loaded, going to the HTML tab does not have any
> > > images (like the '+' for the tree, etc). It uses the system style (in
> > > my case, dark gray for the background), instead of white. Every tab
> > > shows the above error, as well as any commands I've tried to run, like
> > > '>>> 1'. The said commands do not do anything at all.
> > > Started from the terminal, firefox has the following output:
I've just installed latest nightly build, as advised.
Created a fresh profile, and installed my build of fbug (taken from
code just checked out from svn), and tried 1.2 release linked from
getfirebug.com - neither fixed the issue, still seeing corrupt
output.
On 18 Apr, 17:37, "Mike Shaver" <mike.sha...@gmail.com> wrote:
> I've just installed latest nightly build, as advised.
> Created a fresh profile, and installed my build of fbug (taken from
> code just checked out from svn), and tried 1.2 release linked from
> getfirebug.com - neither fixed the issue, still seeing corrupt
> output.
> On 18 Apr, 17:37, "Mike Shaver" <mike.sha...@gmail.com> wrote:
> Could anybody please test this even with Firebug 1.2.0a19 (revision
> 545)?
> Honza
> On Apr 18, 10:06 pm, Darren <darren.mothers...@gmail.com> wrote:
> > No.
> > I've just installed latest nightly build, as advised.
> > Created a fresh profile, and installed my build of fbug (taken from
> > code just checked out from svn), and tried 1.2 release linked from
> > getfirebug.com - neither fixed the issue, still seeing corrupt
> > output.
> > On 18 Apr, 17:37, "Mike Shaver" <mike.sha...@gmail.com> wrote:
I set browser.dom.window.dump.enabled = true in about:config and ran
firefox-3.0 from the command line and I get this output when I open
Firebug in a new window (via a right click on the "bug" icon and
selecting "Open in new window"):
errors.observe, no FirebugContext in chrome://browser/content/browser.xul
errors.observe dropping XPConnect JavaScript no context
errors.observe, no FirebugContext in chrome://browser/content/browser.xul
errors.observe dropping XPConnect JavaScript no context
chrome.initializeUI fails sees object with typeof: 'object'; object
contains:
[message]=enableSystemPagesLink is null;
[fileName]=chrome://firebug/content/chrome.js;
[lineNumber]=506;
[stack]=()@chrome://firebug/content/chrome.js:506
([object XULElement],null)@chrome://firebug/content/chrome.js:246
()@chrome://firebug/content/chrome.js:171
browser2Loaded([object Event])@chrome://firebug/content/chrome.js:1111
;
[name]=TypeError;
I hope this helps. If you need any more output, let me know.
On Apr 18, 4:42 pm, DivineGod <Divine...@gmail.com> wrote:
> I think this must be a firefox problem. The 1.2.0a19X is also not
> working properly.
> I'm using latest nightly build on linux.
> On Apr 18, 11:02 pm, Jan Odvarko <odva...@gmail.com> wrote:
> > Could anybody please test this even with Firebug 1.2.0a19 (revision
> > 545)?
> > Honza
> > On Apr 18, 10:06 pm, Darren <darren.mothers...@gmail.com> wrote:
> > > No.
> > > I've just installed latest nightly build, as advised.
> > > Created a fresh profile, and installed my build of fbug (taken from
> > > code just checked out from svn), and tried 1.2 release linked from
> > > getfirebug.com - neither fixed the issue, still seeing corrupt
> > > output.
> I set browser.dom.window.dump.enabled = true in about:config and ran
> firefox-3.0 from the command line and I get this output when I open
> Firebug in a new window (via a right click on the "bug" icon and
> selecting "Open in new window"):
> errors.observe, no FirebugContext in chrome://browser/content/browser.xul
> errors.observe dropping XPConnect JavaScript no context
> errors.observe, no FirebugContext in chrome://browser/content/browser.xul
> errors.observe dropping XPConnect JavaScript no context
> chrome.initializeUI fails sees object with typeof: 'object'; object
> contains:
> [message]=enableSystemPagesLink is null;
> [fileName]=chrome://firebug/content/chrome.js;
> [lineNumber]=506;
> [stack]=()@chrome://firebug/content/chrome.js:506
> ([object XULElement],null)@chrome://firebug/content/chrome.js:246
> ()@chrome://firebug/content/chrome.js:171
> browser2Loaded([object Event])@chrome://firebug/content/chrome.js:1111
> ;
> [name]=TypeError;
> I hope this helps. If you need any more output, let me know.
> On Apr 18, 4:42 pm, DivineGod <Divine...@gmail.com> wrote:
> > I think this must be a firefox problem. The 1.2.0a19X is also not
> > working properly.
> > I'm using latest nightly build on linux.
> > On Apr 18, 11:02 pm, Jan Odvarko <odva...@gmail.com> wrote:
> > > Could anybody please test this even with Firebug 1.2.0a19 (revision
> > > 545)?
> > > Honza
> > > On Apr 18, 10:06 pm, Darren <darren.mothers...@gmail.com> wrote:
> > > > No.
> > > > I've just installed latest nightly build, as advised.
> > > > Created a fresh profile, and installed my build of fbug (taken from
> > > > code just checked out from svn), and tried 1.2 release linked from
> > > > getfirebug.com - neither fixed the issue, still seeing corrupt
> > > > output.
> Could you please, check the "PANELS" and "INITIALIZE" options
> in the FBTrace panel, restart Firebug and send the logs?
> Honza
> On Apr 19, 1:33 am, Bryan Forbes <br...@reigndropsfall.net> wrote:
> > I set browser.dom.window.dump.enabled = true in about:config and ran
> > firefox-3.0 from the command line and I get this output when I open
> > Firebug in a new window (via a right click on the "bug" icon and
> > selecting "Open in new window"):
> > errors.observe, no FirebugContext in chrome://browser/content/browser.xul
> > errors.observe dropping XPConnect JavaScript no context
> > errors.observe, no FirebugContext in chrome://browser/content/browser.xul
> > errors.observe dropping XPConnect JavaScript no context
> > chrome.initializeUI fails sees object with typeof: 'object'; object
> > contains:
> > [message]=enableSystemPagesLink is null;
> > [fileName]=chrome://firebug/content/chrome.js;
> > [lineNumber]=506;
> > [stack]=()@chrome://firebug/content/chrome.js:506
> > ([object XULElement],null)@chrome://firebug/content/chrome.js:246
> > ()@chrome://firebug/content/chrome.js:171
> > browser2Loaded([object Event])@chrome://firebug/content/chrome.js:1111
> > ;
> > [name]=TypeError;
> > I hope this helps. If you need any more output, let me know.
> > On Apr 18, 4:42 pm, DivineGod <Divine...@gmail.com> wrote:
> > > I think this must be a firefox problem. The 1.2.0a19X is also not
> > > working properly.
> > > I'm using latest nightly build on linux.
> > > On Apr 18, 11:02 pm, Jan Odvarko <odva...@gmail.com> wrote:
> > > > Could anybody please test this even with Firebug 1.2.0a19 (revision
> > > > 545)?
> > > > Honza
> > > > On Apr 18, 10:06 pm, Darren <darren.mothers...@gmail.com> wrote:
> > > > > No.
> > > > > I've just installed latest nightly build, as advised.
> > > > > Created a fresh profile, and installed my build of fbug (taken from
> > > > > code just checked out from svn), and tried 1.2 release linked from
> > > > > getfirebug.com - neither fixed the issue, still seeing corrupt
> > > > > output.
> Could you please, check the "PANELS" and "INITIALIZE" options
> in the FBTrace panel, restart Firebug and send the logs?
> Honza
> On Apr 19, 1:33 am, Bryan Forbes <br...@reigndropsfall.net> wrote:
> > I set browser.dom.window.dump.enabled = true in about:config and ran
> > firefox-3.0 from the command line and I get this output when I open
> > Firebug in a new window (via a right click on the "bug" icon and
> > selecting "Open in new window"):
> > errors.observe, no FirebugContext in chrome://browser/content/browser.xul
> > errors.observe dropping XPConnect JavaScript no context
> > errors.observe, no FirebugContext in chrome://browser/content/browser.xul
> > errors.observe dropping XPConnect JavaScript no context
> > chrome.initializeUI fails sees object with typeof: 'object'; object
> > contains:
> > [message]=enableSystemPagesLink is null;
> > [fileName]=chrome://firebug/content/chrome.js;
> > [lineNumber]=506;
> > [stack]=()@chrome://firebug/content/chrome.js:506
> > ([object XULElement],null)@chrome://firebug/content/chrome.js:246
> > ()@chrome://firebug/content/chrome.js:171
> > browser2Loaded([object Event])@chrome://firebug/content/chrome.js:1111
> > ;
> > [name]=TypeError;
> > I hope this helps. If you need any more output, let me know.
> > On Apr 18, 4:42 pm, DivineGod <Divine...@gmail.com> wrote:
> > > I think this must be a firefox problem. The 1.2.0a19X is also not
> > > working properly.
> > > I'm using latest nightly build on linux.
> > > On Apr 18, 11:02 pm, Jan Odvarko <odva...@gmail.com> wrote:
> > > > Could anybody please test this even with Firebug 1.2.0a19 (revision
> > > > 545)?
> > > > Honza
> > > > On Apr 18, 10:06 pm, Darren <darren.mothers...@gmail.com> wrote:
> > > > > No.
> > > > > I've just installed latest nightly build, as advised.
> > > > > Created a fresh profile, and installed my build of fbug (taken from
> > > > > code just checked out from svn), and tried 1.2 release linked from
> > > > > getfirebug.com - neither fixed the issue, still seeing corrupt
> > > > > output.
> Could you please, check the "PANELS" and "INITIALIZE" options
> in the FBTrace panel, restart Firebug and send the logs?
> Honza
> On Apr 19, 1:33 am, Bryan Forbes <br...@reigndropsfall.net> wrote:
> > I set browser.dom.window.dump.enabled = true in about:config and ran
> > firefox-3.0 from the command line and I get this output when I open
> > Firebug in a new window (via a right click on the "bug" icon and
> > selecting "Open in new window"):
> > errors.observe, no FirebugContext in chrome://browser/content/browser.xul
> > errors.observe dropping XPConnect JavaScript no context
> > errors.observe, no FirebugContext in chrome://browser/content/browser.xul
> > errors.observe dropping XPConnect JavaScript no context
> > chrome.initializeUI fails sees object with typeof: 'object'; object
> > contains:
> > [message]=enableSystemPagesLink is null;
> > [fileName]=chrome://firebug/content/chrome.js;
> > [lineNumber]=506;
> > [stack]=()@chrome://firebug/content/chrome.js:506
> > ([object XULElement],null)@chrome://firebug/content/chrome.js:246
> > ()@chrome://firebug/content/chrome.js:171
> > browser2Loaded([object Event])@chrome://firebug/content/chrome.js:1111
> > ;
> > [name]=TypeError;
> > I hope this helps. If you need any more output, let me know.
> > On Apr 18, 4:42 pm, DivineGod <Divine...@gmail.com> wrote:
> > > I think this must be a firefox problem. The 1.2.0a19X is also not
> > > working properly.
> > > I'm using latest nightly build on linux.
> > > On Apr 18, 11:02 pm, Jan Odvarko <odva...@gmail.com> wrote:
> > > > Could anybody please test this even with Firebug 1.2.0a19 (revision
> > > > 545)?
> > > > Honza
> > > > On Apr 18, 10:06 pm, Darren <darren.mothers...@gmail.com> wrote:
> > > > > No.
> > > > > I've just installed latest nightly build, as advised.
> > > > > Created a fresh profile, and installed my build of fbug (taken from
> > > > > code just checked out from svn), and tried 1.2 release linked from
> > > > > getfirebug.com - neither fixed the issue, still seeing corrupt
> > > > > output.
> > > I set browser.dom.window.dump.enabled = true in about:config and ran
> > > firefox-3.0 from the command line and I get this output when I open
> > > Firebug in a new window (via a right click on the "bug" icon and
> > > selecting "Open in new window"):
> > > errors.observe, no FirebugContext in chrome://browser/content/browser.xul
> > > errors.observe dropping XPConnect JavaScript no context
> > > errors.observe, no FirebugContext in chrome://browser/content/browser.xul
> > > errors.observe dropping XPConnect JavaScript no context
> > > chrome.initializeUI fails sees object with typeof: 'object'; object
> > > contains:
> > > [message]=enableSystemPagesLink is null;
> > > [fileName]=chrome://firebug/content/chrome.js;
> > > [lineNumber]=506;
> > > [stack]=()@chrome://firebug/content/chrome.js:506
> > > ([object XULElement],null)@chrome://firebug/content/chrome.js:246
> > > ()@chrome://firebug/content/chrome.js:171
> > > browser2Loaded([object Event])@chrome://firebug/content/chrome.js:1111
> > > ;
> > > [name]=TypeError;
> > > I hope this helps. If you need any more output, let me know.
> > > > I think this must be a firefox problem. The 1.2.0a19X is also not
> > > > working properly.
> > > > I'm using latest nightly build on linux.
> > > > On Apr 18, 11:02 pm, Jan Odvarko <odva...@gmail.com> wrote:
> > > > > Could anybody please test this even with Firebug 1.2.0a19 (revision
> > > > > 545)?
> > > > > Honza
> > > > > On Apr 18, 10:06 pm, Darren <darren.mothers...@gmail.com> wrote:
> > > > > > No.
> > > > > > I've just installed latest nightly build, as advised.
> > > > > > Created a fresh profile, and installed my build of fbug (taken from
> > > > > > code just checked out from svn), and tried 1.2 release linked from
> > > > > > getfirebug.com - neither fixed the issue, still seeing corrupt
> > > > > > output.
Revision 562 works for me in Firefox 3b5 on Ubuntu Hardy. DOM
inspector, and javascript debugger seems to work fine, but it still
open in a new window and not in a pane inside the browser.
On Apr 19, 7:46 pm, Francisco <nfla...@gmail.com> wrote:
> > > > I set browser.dom.window.dump.enabled = true in about:config and ran
> > > > firefox-3.0 from the command line and I get this output when I open
> > > > Firebug in a new window (via a right click on the "bug" icon and
> > > > selecting "Open in new window"):
> > > > > I think this must be a firefox problem. The 1.2.0a19X is also not
> > > > > working properly.
> > > > > I'm using latest nightly build on linux.
> > > > > On Apr 18, 11:02 pm, Jan Odvarko <odva...@gmail.com> wrote:
> > > > > > Could anybody please test this even with Firebug 1.2.0a19 (revision
> > > > > > 545)?
> > > > > > Honza
> > > > > > On Apr 18, 10:06 pm, Darren <darren.mothers...@gmail.com> wrote:
> > > > > > > No.
> > > > > > > I've just installed latest nightly build, as advised.
> > > > > > > Created a fresh profile, and installed my build of fbug (taken from
> > > > > > > code just checked out from svn), and tried 1.2 release linked from
> > > > > > > getfirebug.com - neither fixed the issue, still seeing corrupt
> > > > > > > output.
The last Ubuntu Hardy updates combined with the new Firebug 1.2.0a21X
fixes these problems for me. Although I haven't checked more complex
functions, basic DOM/CSS editing works. Great stuff!