Comment 396 for bug 191889

@Alexander: I apologize for the terse post earlier. I love Ubuntu, especially the Kubuntu variant and all my computers run Jaunty (except for my server which is still Intrepid). My post was made at 2am my time after being up since 7am working all day, driving 2.5 hours at 4pm and working from 8pm to 1am. I was stressed and should not have posted so late. I found out the solution for the localhost problem was to switch Firefox to offline mode. It's just unfortunate that Firefox isn't smart enough to respond automatically by using a local dns test first or if an ip/ipv6 address is given within a known loop back range (this is a standard) or an ip that is local to an interface regardless of NetworkManager's status. This first seems simple to me, but maybe Firefox doesn't have sufficient privileges for the second? I'm not saying that Firefox should ignore NetworkManager, but instead it should check NetworkManager first to see if we're online since that is the fastest way to know, and fall back to the other tests as a last resort. To rely solely on NetworkManager is to cause many Web Developers (who often use the local machine as a web server), and those who use their machines in a disconnected fashion with web programs, a great disservice. We are trying to make things easier, not harder for everyone. Most people wouldn't think that you have to switch to offline mode to access localhost when you're not connected to a network. I always thought offline mode was reserved to those on cellular, satelite or dial-up connections who don't want their internet activated to reduce possible charges.
So, should I open a bug report with this information?