After upgrade to Firefox 18 system proxy settings don't work correctly. At the same time, Firefox 17, IE and Opera work as expected. I guess, this is a newly introduced bug. Could you please check it?
hello maxvor, there are some proxy related bugs in firefox 18 (but when i remember correctly most of them affected linux & osx systems) which will be addressed in a firefox 18.0.1 release soon, you might want to look out for that...
I noticed a lag in pages loading in FF 17.0.2 immediately after the most recent Windows update so I installed FF 18. As soon as it installed pages would not load at all and when I checked support it said that my antivirus program was probably blocking it and I should make the new FF an exception. I then discovered that my Norton Internet Security 2011 had been completely wiped out. I had to completely uninstall and reinstall Norton. Then I uninstalled FF 18 and went back to 17.0.2 and now everything is working fine.
I am also having this issue- every FF install that has been updated to 18.0 stops working (XP machines). Never had this issue with FF before, or any other browser. When I remove the proxy settings (uncheck "use system proxy settings") on any of these machines, FF begins working immediately.
Firefox 18.0.1 is now live, and it fixes the proxy issues found in Firefox 18. Please update to that version.
FF 18.0.1 still does not resolve the proxy issue. When I initially open FF I have to reset the proxy configuration to 'No Proxy' because FF 18 always selects the 'Manual Proxy Configuration' when the application is closed and reopened?! Can this be corrected . . .
Thanks in advance . . . Love my Functional FF
My experience shows that Windows has the same problem as well. I have an 8gb machine Win 7 64Bit OS. It appears that this problem has been passed from 18.0 thru 18.0.1. I have normally chosen the 'No Proxy' option in prior versions. But since the introduction of 18.0, I briefly had the proxy problem but it was quickly resolved from the developers of this app. I allow FF to auto dl and install so when 18.0.1 was installed and this problem reappeared, I knew someone had to have picked up a prior module or something and reintroduced the same problem all over again.
Can anyone share a timeframe for resolving this issue?
Thanks in advance . . . TomJ
Thanks madperson for this clue. I followed the info layed out from the link and when I examine the 'user.js" I don't find an entry that relates to the proxy. I am including the lines I find in ths file for your review. Please let me know if you see anything out of the ordinary that may be relevant:
BTW: I am curious as to where the "BabylonToolbar" comes from because I have no toolbar by this name.
Thanks in advance . . .