I clearly remember that 2 months ago whenever i had any javascript error , It was shown as red text in Firefox console , and i knew what is the problem.
But now its not doing that.
I had one undefined variable and i was using that. But i didn't knew. i had to waste 1 hour to find that.
But firebug didn't show anything on console. It was showing before 2-3 months back
Same in Firefox and Google chrome
What should i do
Please try firebug 1.2b12 from http://getfirebug.com/releases/firebug.
Please check that you have Console enabled and Console > Options >
Javascript Errors checked.
If you still have a problem please open a bug report and attach a
complete test case.
Source : https://groups.google.com/forum/?fromgroups=#!topic/firebug/HgpEGNLZ18c
Related
I'm using the latest FF (108.0.1)
In the developer tools, when I submit an XHR-Request, I used to see the request's HTML-Rendering in the «Answer»-Tab of the console. This stopped working like 2 or 3 versions ago.
Now all I get is a blank page. If I switch to «unformatted» it shows the HTML-Code of the response.
When I use the «Network»-Tab, I do see the HTML Response. But the interaction with the result doesn't work anymore.
Explanation: I'm using Typo3's DebuggerUtility::var_dump() which creates a nice rendering of objects and arrays. I used to be able to expand the entries with a «plus»-sign, in the HTML-View of the console. Which is very handy. This is not working when I use the Network-Tab of the Dev-Tools.
Any ideas how to get that functionality back?
This bug got fixed a few days ago. That means it is working again in Firefox 110.
Though note that JavaScript was never executed in that preview because of security reasons, as far as I can tell. The output is pure HTML plus CSS like in your screenshot of the Response tab in the Network panel saying that JavaScript needs to be enabled.
So, the toggle there may only work if it is using a browser internal feature like the <summary> and <details> elements.
I am doing some debuging from the server and I was able to previously get a preview in the google chrome network tab, what ever server answered would get rendered clearly if I used dd() or dump()
now all I get is bunch of html and I can't make anything out.
You can see here what I see
This stuff used to be like this if I went to Response tab instead of Preview tab, but now even Preview tab does not make any sense.
Never had a problem with this before. Anyone else noticed or had this problem? How to debug a problem I have on server when I can't dd or dump to inspect what went wrong with save operation?
The HTML you are seeing looks like the default markup of the error page. You could check the storage/logs/laravel.log file to see whats causing the error
I get this error on Firefox 24.0, and I have firebug, fireftp and colorzilla installed. This just started happening recently. I have searched for this problem but all the topics come up as being from 2-4 years back, mostly Firefox versions 3 through 4.
Anyone have an idea how to fix this? They work in IE OK.
This also appears to do this for the main list page:
https://drive.google.com/?pli=1&authuser=0#
that just hangs without showing ANY of my docs.
I struggled with this for weeks.
Finally what resolved it is pretty stupid... Not sure if it will work again.
But maybe it will help someone!
Instead of going to drive.google.com I just opened docs.google.com and after it forwarded me to drive everything started to work... without even a cache clean!
Pretty funny!?
In jsfiddle.net, I have this simple code:
console.log('yep');
alert('hello');
I can see the alert window but nothing in my firebug console.
Is there a reason why ?
I'm encountering it as well on my FF15.
In my case, it is caused by the built-in "web console" in "web developer"
Ctrl+Shift+K
https://developer.mozilla.org/en-US/docs/Tools/Web_Console
Beginning with Firefox 4, the old Error Console has been deprecated in favor of the new, improved Web Console. The Web Console is something of a heads-up display for the web, letting you view error messages and other logged information. In addition, there are methods you can call to output information to the console, making it a useful debugging aid, and you can evaluate JavaScript on the fly.
I'm new to using console.log (I used to use alert()s) and was wondering why I couldn't see console.log messages in Firebug too.
After a several minutes of web searching I realised the console mode was set to 'Debug Info'. Clicking the 'All' button made all my messages appear.
The OP didn't make this particular mistake, admittedly. It's a rookie error, but still non-obvious enough (I haven't used Firebug for a while) to bring me here before I managed to figure it out.
This issue has been fixed in Firebug 1.11.0a5. More info is here
I just had the same issue with firefox 29 Beta (and Australis) Just restart the browser :)
EDIT : seems like its it's not true : on the first page load, it display the log, on the others not (need to open the page in a new tab). Apparently it's queryLoader2 jQuery plugin
In a lot of cases when my prototype.js javascript code hits an error, I don't get any error notification, line number, etc. I usually end up tracing through my code with alert statement until I find where it dies. Is there a better way to track down these errors?
Depends on browser, but there are some very good ways of handling errors. If you are using firefox, you can install FireBug and then use:
console.log('like an alert but in the firebug window');
It's alot quicker than pressing ok, then ok, then ok...
http://getfirebug.com/
Firebug also has an amazing JS error debugger, and gives great feedback as to what is wrong with your code. A must have if you ask me!
I already use Firebug ...
Is this case, try Chrome — I find that Firefox fails to notify me of errors in my code that uses Prototype.js, but Chrome is fine. Not that I'm a huge fan of Google over Mozilla.