Why does Firebug say there is No Javascript on this page when there are clearly loads of JavaScript on the page. I even reloaded the page several time to make sure but it still show the same message.
It never used to do that before, but all of a sudden it misbehaves.
Is it because of some configuration issues or because of something else?
As of Firefox version 50, it seems that Firebug will no longer work as Mozilla are migrating to Firefox Devtools. The tab Tools/Web Developer has a 'debugger' option. See this page for a discussion on the migration. Read all the posts dated 19 November for further information.
It seems to me that the option gives less functionality but Firebug per se is never going to be fixed for Firefox 50 and beyond
EDIT 2017 April
This answer is now outdated and I'm not even testing it anymore because I'm no longer using Firebug (a shame, I loved it years ago in a time it was The tool of trade for web developing).
EDIT 2014 November
The original answer is now more than a year outdated due to firebug evolution.
Thanks to #AmadeusDrZaius to keep it on tracks
Answer for outdated firebug versions
For anyone still with this problem after updating Firebug.
Just click Clear Activation List option inside the Firebug menu.
For those who can't find it, note that "Clear Activation List" shows up in the dropdown from the Firebug icon in the toolbar, but not the Tools > Web Developer > Firebug menu.
I guess due to the bug previous hitting your working page it stays listed as "no activate FB for this site please".
I encountered No Javascript on this page after upgrading Firefox to ver 50.0, with Firebug ver 2.0.18. I tried refreshing Firefox, even completely uninstall Firefox and installed again. Nothing works for me.
A couple of hours later, I downgraded Firefox to 49.0.2, and voila, it works right away. I downloaded the old version here.
I tried everything on this list and nothing worked for me except resetting Firefox like so:
https://support.mozilla.org/en-US/kb/reset-firefox-easily-fix-problems
I realize there are already 10 answers to this question, but in my case none of them helped. I'm running Firefox version 39.0 and Firebug version 2.0.11. The only fix is to completely restart Firefox (i.e. not just the tab or instance with the problem).
Perhaps it's due to Firefox's over-usage of memory, or maybe there's a bug in Firebug. I can't speak to that, but what I do know is it didn't work. I killed Firefox, opened the exact same page again with no changes made and now it works. This has happened to me numerous times and a complete restart always fixes it, but that's the only thing that does.
Since Firefox 49.0 and Firebug 2.0.18 the Script panel is broken. This is due to some internal Firefox API changes. And because Firebug is officially discontinued, this unfortunately won't get fixed anymore.
There was also a bug in Firebug 2.0.11 (and below) in combination with Firefox 39.0 causing this problem. This bug is filed as issue 7918.
It happens when the Script panel is enabled and you close Firebug and reopen it.
You can see two related error messages logged to the Browser Console (can be opened via Ctrl+Shift+J or Firebug menu > Developer > Browser Console):
error occurred while processing 'attach: TypeError: docShell is null
Stack: getChildDocShells#resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:53:7
...
and
onPacket threw an exception: Error: Server did not specify an actor, dropping packet: {"error":"unknownError","message":"error occurred while processing 'attach: TypeError: docShell is null\nStack: getChildDocShells#resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:53:7
...
Solution:
The only solution until this bug is fixed is to restart Firefox completely.
Similar things have happened to me because I forgot to add the closing tag.
DON'T do this:
<script src="some.url" type="text/javascript">
or
<script src="some.url" type="text/javascript"/>
DO this instead:
<script src="some.url" type="text/javascript"></script>
The same problem just happened to me. I thought that it was a problem in my scripts, but I checked google.com and the problem persisted.
My problem was that I had updated my version of FF and kept the old version of FireBug. When I updated FireBug and everything was solved.
From firefox 49, the fire bug will be built in and it is called fire-bug next. So the fire bug add on won't work properly and no issues will be solved. So you can use firefox inspector. See here for details information
If the problem only shows up on a single page, check that your script folder is referenced from current folder (".") or that's reachable from the server root ("/").
<script src="./scripts/pagescripts.js" type="text/javascript"></script>
may not be the same as
<script src="/scripts/pagescripts.js" type="text/javascript"></script>
As mentioned, sometimes there's a Javascript syntax error that invalidates the whole script. But I have also had this, and simply opening up the page in a new tab or window and refreshing firebug (disable, enable) gets the javascript to show up again.
One time this caught me out was when I published one of my sites and I was checking it out. No Javascript was working, there were no errors in the console and firebug showed no scripts.
It turned out that in that instance, I'd forgotten to allow the site in NoScript - so there really were no scripts being loaded.
Not sure if that's the problem you're facing but it's worth being aware of.
I also got this error when attempting to use Ajax to a different server than the one serving up the page. JavaScript only allows Ajax access to the server that served up the page.
This problem is STILL happening (Aug 2015) with Firefox 39.0.3 and Firebug 2.0.11
For people saying the code is wrong or missing end tags etc. all I did to get all the javascript to reappear in tab was to shut down Firefox and restart it. I didn't change anything. Also that "Clear Activation List" option didn't work (no idea what that means)
I upvoted #Tom_Thomson's answer above, but I am wondering if simply removing and then reinstalling the Firebug add-on might not have accomplished the same thing without losing all the other stuff like bookmarks.
FWIW this problem is still happening in August 2016. I'm using Firebug 2.0.17 with Firefox Dev Edition 50.0a2.
As a workaround, I'm able to use the Developer Tools, though they are not as robust as Firebug (when it's working).
Well Firefox native Inspector is good... I know that you will miss some things, but in general we can survive with it. The good news is... less one addon, FF will be faster :)
Related
I'm going to try to explain an issue that scratch my head...
When I open this website for the first time after opening Firefox (v43.0.3), the UI freeze during about 20 seconds and I don't undersand why. For example you can see that the background image appear after almost 20 seconds...
So, I used firebug net panel to try to understand where the problem comes from and I notice that the page load event is very long but I can't see any tasks executing during this event.
here is a screenshot of firebug Net Panel
When I open the website with Chrome it works fine, does someone has ever encounter that kind of problem ?
I hope that makes sense, thank you in advance.
You're making 31 requests (according to my NET panel - FireBug) which add to 323ms (at least in my case). Your background image is loading ~1s after. Maybe if you'd try to reorganize all that sprites you're requesting into less files - but it seems fair as loading time for me.
I once had a problem with Firebug itself. I had to turn it off and\or uninstall to get the page load normally on Firefox.
In my case it was an effect of problem between Firebug and Telerik Kendo JS Library.
Maybe you have a problem similar issue.
Thanks for your answers, indeed it seem's to comes from my firefox configuration or addons/plugins.
I use a Firefox pre-configured by my socity, so I installed a portable firefox to try if it works and the website is loading normaly.
Now I just have to find from whitch config or addons/plugins the problem comes from, thanks again !
Chrome itself appears to work fine but I'm having problems with Developers Tools. After a short period of time it becomes unresponsive and the following dialog pops up...
Is this a known bug, can or will it be fixed soon? Also, the meantime what should I do, how can I roll back to older working version of Chrome?
I use Chrome and Developer Tools extensively and this is causing a major headache, so any advise would be welcome.
It is a known bug that got pushed with v32. I have not seen anything about fixing it yet though.
It happens with any model window (which includes devtools) or when Chrome is running in app mode.
Chrome isn't actually crashing and you can still continue to use it, but that will continually pop up with devtools open.
The issue has been fixed as of today's (1/28/2014) update. Version: 32.0.1700.102 m
I started getting this problem as well.
In searching, I came across this issue: "Page(s) Unresponsive" error messages in 32+.
As best I figured out, the bug is related to:
Windows 7/8 with Aero Theme
Scrollbars on pages (such as in the developer console)
Pages with popups (in particular Window.open() calls)
I guess they are slated to push the fix into version 33...and maybe leave the stable* 32 how it is (I hope not).
So there are a few options:
Switch away from Aero Theme until version 33 is in stable
Upgrade to the beta channel, i.e. version 33
Click on the Wait button every 30 seconds whenever the chrome developer tools is open (Don't try this at home).
Update:
Chrome has released a hotfix into the version 32 stable channel.
The issue is resolved in Chrome Canary 34.0.1799.0. Read more:
Issue 335248: "Page(s) Unresponsive" error messages in 32+
#elewinso, Alternate place to look for the same registry key to disable Chrome autoupdate is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Update..
Also, is there a way I can get notified when the next update happens? or, when can I remove this key?
upgrade chrome to Version 32.0.1700.102 m this fixes the problem
I feel like I'm going crazy but alert() and console.log() refuses to work anywhere on Firefox 26.
At first I thought it was my own website's problem, but I cannot for the life of me to get it to work via javascript: urls, Firebug, I even tried it in jsfiddle.net by just putting alert('test'); in the script panel.
Tried uninstalling and installing again, no luck.
The only extension I'm running is Firebug.
Heck, Stackoverflow didn't even prompt me about leaving when I accidentally clicked the back button while writing this.
Also yes, I made sure there was some content inside the alert() and console.log()
What I mean by not working is that Firefox treats the code as if it were non-existent, nothing happens.
Once again, here's my environment:
Browser: Firefox 26.0
OS: Windows 8.1 Pro
Issue: alert(), console.log(), and apparently prompt() doesn't work
If anyone might know why this is happening, I would highly appreciate an answer.
UPDATE
Following Pointy's comment, it appears that both alert() and console.log() work as expected on the New Tab Page, but nowhere else
You might want to try re-installing Firebug:
console.log in firefox is not working?
PS:
I happen to be running a similar configuration (including FF 26) ... and things work fine for me. IMHO...
PPS:
You might also try setting "about:config, prompts.tab_modal.enabled = false":
https://bugzilla.mozilla.org/show_bug.cgi?id=613752
The default is "true", my FF 26 is set "true" and things are working for me ... but who knows. If reinstalling Firebug doesn't help, maybe it's worth a shot?
Silly but, in firebug can you check if window.alert and window.console are defined.... and if yes then, can you check if window.alert('hi') works ?
Thanks for all the help guys, in the end I used Revo Uninstaller to completely and absolutely wipe Firefox from my system, then installed it again. Seems to be working now, the original uninstaller most likely didn't remove whatever was causing the problem.
I have same bug when i using Ghostery extension. Disable Ghostery and reload page. Lets check at https://getfirebug.com/tests/head/console/api/log.html
I had a similar issue, on IE v11.0.10 and Chrome Canary v38.0.2114. Duplicate function name turnout to be the issue. Worth doing a quick check for function names in Javascript file.
You can use the Firefox console with CTRL + SHIFT + K
Related: https://support.mozilla.org/en-US/questions/876916
So, I have a heavy page that does a ton of JavaScript and has some huge SVG elements. It's been working great in Webkit/Gecko, but I am now testing in IE and the page doesn't load (well, it loads but most of my JavaScript never seems to run).
First thing I did was drop Firebug Lite into the page to see what's happening, but after I did that, the page loads and functions perfectly in IE! However I don't see the little bug icon to get to the console.
Since I still don't have a console, I'm having trouble figuring out what's happening. Perhaps Firebug defined some variables (console?) that my page needed? Can anyone give some guidance on how to proceed here?
I'll make this an answer since my comment seemed to solve your problem.
If you have uncommented console.log code when running in IE, IE will bark errors at you and fail to properly run the script. Opening a console (IE or Firebug Lite) typically allows the code to run, however you obviously cannot count on your visitors doing this, therefore it's always best to remove or comment out all console.log() calls when releasing production code.
Okay I think I figured this out. console is only defined in IE8+ IF the developer console has been opened and the page refreshed. So including Firebug Lite probably made my page work by itself defining console.
So I'll just have to comment out my console.log statements when the page is public.
I'm using Firebug to develop a JS app. All of a sudden, when I got to the page, it appears that I do not have JS enabled - the <noscript> warnings are rendered, and nothing works. When I go to the same page in Chrome, everything works fine.
What could be happening? I reverted recent changes back to a point where it worked, but it's still failing.
UPDATE: I just went back to the page in question, and now it works fine. I had been working on it in Chrome. Odd.
Honestly, I've had to disable Firebug entirely. Way too many errors and bung-eyes there.
Worked wonders for a long time, but recently... not so.
I've switched to Chrome + Developer extension - which does fall short, but it does the trick.