i know this question might get voted down and be closed but i have to put it out there
im windows user and i got familiar with firefox in the bad old days of IE reign
i love firefox specially after i become a web developer and started to work with wonderful add-ons
but recent changes has made me to move to chrome more and more every day specifically i have to mention death of beloved firebug
i hate the firefox developer console , it feels awkward and clunky and primitive compare to firebug and its not as user friendly as firebug
i have to ask , is it me or anyone else feels the same ? cuz i've searched around and it doesn't seem to bother anyone else !
here is what bothers me the most .... modern web apps rely heavily on ajax calls , for some reason i cant find preview for ajax calls response in the firefox developer tools ... i can see server response as code but not rendered preview of server response
and i say i cant find it becuz i cant imagine possibility of not having preview .... just imagine your using a framework and it returns a stack error with lots of html/css style , its impossible to find the actual error among the heap of codes in developer tools response section
so aside from the rant , basically im hoping someone to say there is a preview and this is how you can activated it !
Unfortunately, the preview for responses got removed in Firefox 55, obviously under the incorrect assumption that it duplicated some other UI.
Luckily it was added back for Firefox 59, now placed within the Response panel.
Here's a screenshot for how this looks like on this page:
Related
Not sure if this is the right place to ask this question, but I am seeing an annoying issue when debugging ASP MVC applications on visual studio.
After pressing F5, Firefox opens and everything works normally, but after doing this a few times, when I try searching anything on google from the same network I am presented with multiple captchas (usually 2 at a time).
It seems that Google thinks there is some suspicious activity going on on my computer, but of course everything is just fine.
I am still able to search normally through Chrome, IE etc.
Has anyone else expereienced this issue? If so is there perhaps an option within VS or in my browser to prevent this from happening?
Well all right, maybe it doesn't kill web development completely... but it's certainly irritating. =)
I have been testing a site recently using various desktop and mobile browsers. So far, the only one that has given me significant trouble is Safari running on the iPhone 5, which uses a level of caching beyond anything I have seen before that seems nearly impossible to get rid of, which I now call Super Caching. This Super Caching has prevented me from testing my site as I am unable to test any changes - not to the css style, back-end c#, front-end javascript, aspx design, nada. I have tried the following methods to attempt to clear the cache for this page (both separately and all together):
Close all tabs in Safari, then close Safari entirely (double tap home button, close Safari icon there)
Settings -> Safari -> Clear History + Settings -> Safari => Clear Cookies and Data. Checking the Website Data after doing this confirms there is nothing there and shows 0 bytes of stored data.
Shut down my phone completely (not just sleep)
Change the url to my site by appending garbage information like ?random=pleasedontcacheme&random2=123
Add code to my site to try and prevent caching... which of course doesn't work because these changes are never retrieved by the phone's browser.
In short, testing has become a small nightmare at the moment. While any tips for how to actually destroy Safari's obnoxious caching would be greatly appreciated, I am more interested in making sure that this does not happen during development in the future. So my question is, for the current Safari browser, what is the best way to stop it from caching a website?
So far I have added the following to the Page_Load of my site's default page:
HttpContext.Current.Response.Cache.SetExpires(DateTime.UtcNow.AddDays(-1));
HttpContext.Current.Response.Cache.SetValidUntilExpires(false);
HttpContext.Current.Response.Cache.SetRevalidation(HttpCacheRevalidation.AllCaches);
HttpContext.Current.Response.Cache.SetCacheability(HttpCacheability.NoCache);
HttpContext.Current.Response.Cache.SetNoStore();
Response.AppendHeader("Cache-Control", "no-cache, no-store, must-revalidate");
Response.AppendHeader("Pragma", "no-cache");
Response.AppendHeader("Expires", "0");
I have also seen others use meta tags, though they have been described as a bit hacky. (As found here).
I am still working towards a way to retake control of my iPhone's cache, but in the meantime, I would like to ask those who might be more experienced with this particular issue how well the above methods work for getting around the caching issue (during development mostly, but also good to know for future reference). Or, are there other solutions that have been found helpful for this browser/system combo?
Thank you very much in advance for any tips or advice. =)
I am building a website that uses Google Visualization API, and it works fine (even in IE), except for production server. Basically:
In all browsers not made by microsoft it works;
In IE8, 9 on the dev server (localhost:8000) it works;
In production, it fails saying 'Your browser does not support charts', which is not true.
No https involved, js is taken from Google, no browser or js errors at all. HTML from dev and production server is the same, I actually checked with the diff tool.
Any ideas on why can this happen or how do I fix this? Example URL: http://publishedin.com/websites/profile/penpen.in/ (graphs are in the left column).
I have similar charts running in IE 9 without a problem. Other people have noticed this problem when there is some kind of code collusion on the page.
So, try creating a page that only runs the charts, nothing else. If it works, there is some code on the page interfering with the chart creation.
I got your charts to run in IE 8 & 9:
http://www.jensbits.com/demos/charts.php
I have found IE to be particularly intolerant of code that confuses it.
I've got this weird bug. The progress bar in IE's bottom-window status bar keeps incrementing very slowly after an Ajax POST. At least that's where I think the problem is.
How can I tell what the hell IE is doing that's causing the progress bar to keep going? In FireFox, I would just look at the Console tab in FireBug and see what's up.
I turned Fiddler on but it doesn't pick up any HTTP requests or responses being sent.
What can I do in IE?
I'm not very experienced in Web debugging but you might try the Developer Tools that come in Internet Explorer 8. It's under the Tools menu, or just hit F12. I think the Profiler tab may be helpful. I had heard somewhere that the IE8 Tools were created to mimic Firebug's feature set as closely as possible.
An another tool for checking HTTP requests is the Debugbar
This might not help if Fiddler isn't picking anything up, but HttpWatch is a great http request debugging tool for IE.
I don't think there is a problem here, earnestly. IE has a bug where it shows that a request has not yet been completed when it has. This has been around for a while now, and I have tested my own applications against it. There is nothing happening and there are no connections waiting for a response, yet the browser still thinks there is an open connection.
i recently discovered this tool for earlier IE versions which can be used in combination with the IE debugger for network profiling and more behind the scenes debugging
http://www.ieinspector.com/httpanalyzer/
open IE ...thn press F12 ...here you will get many menus..to debug script choose "SCRIPT" option..and start debug...and if there is any error on page...thn u will get on Console option..also see on attach image...
Using Firebug v1.20b7 with Firefox v3.0.1 I use firebug a lot for web devlopment.
I have very often the problem that Firebug won't show its web console for seeing the POSTs and GETs. I can view all the other tabs, including the NET tab that gives me a lot of the same information that the CONSOLE tab does.
Curious if anyone else has had this problem, and maybe a solution, or maybe this is a bug of Firebug.
There is a limitation in firebug (or rather, in firefox iteself), which will be fixed in one of the newer Firefox releases.
The bug is caused by the fact that firebug needs to send data a second time to monitor what's going on in the connection.
There's now a special API hook in the firefox trunk that should prevent this workaround in the future, so that firebug can really spy on what's going on :)
Well, 1.20b7 is technically a beta version of Firebug. :)
I've had problems with certain features off and on, but a restart of Firefox seems to fix it more often than not.