Comment 313 for bug 191889

(In reply to comment #114)
> I don't understand why there is still an insistense on this bug being an edge
> case.
>
> There are many situations where NM has to be disabled or ignored. PPP, rutilt,
> manual configuration (static IP).

Not sure about PPP, but the other situations are edge cases. However, breaking things by default for those cases is not acceptable, so I'm planning to disable NM usage by default.

> I find that relying on an optional component is quite heavy handed.

1) There is no "non-optional" component capable of doing what we need. That is a weakness of the Linux (or GTK if you prefer) platform.
2) We don't rely on NetworkManager in order to operate. All we rely on is that IF it is present, it tells us the truth. Unfortunately it doesn't; that's just a fixable bug in Networkmanager and not our fault. Of course since the bug isn't fixed, it is our fault to trust NetworkManager, so we should stop doing that.

> Work Offline should be a user option. not automatically set up.

No, it's very useful to have it work automatically. We have that for Windows and people want it on all platforms. I'm 100% sure that when we turn this off by default for Linux, people will start to complain that Firefox doesn't have feature parity on Linux and so obviously Mozilla hates Linux.

> Alternativelly there should be an option (not hidden) where the user can check
> if he/she wants to rely on the NM for connectivity.

Most people who need that would never find it.

> Having it always check the NM is missguided. This is a bug.

Now that I know more about the state of NetworkManager, I agree.