Comment 394 for bug 191889

Ok, it was reported in February, now it is well into May, Jaunty has been released already. Has anyone even tried to fix this? I think the about:config workaround above does seem to fix it for Firefox, but is there a reason why we shouldn't just force that as a default or if that isn't feasible to permit browsing to the local loopback/net addresses at least regardless of network status? NetworkManager does many great things, but making programs dependent upon it is ridiculous. It doesn't always know if a particular address will be available or not. If I am travelling and I do not have a network connection Firefox prevents me from browsing to localhost. That is plain stupid! Konqueror browses to localhost just fine without a network. I am running Jaunty with the latest updates installed, but it still isn't fixed.