> They edited the bug and > turned it into a documentation issue instead of looking at the actual > request to provide an easy (default) setting ensuring real privacy.
I agree that an interface requiring this much work to achieve a theoretically possible configuration is a software bug. However, having a documentation page called "How to stop Firefox from making automatic connections" that doesn't stop Firefox from making automatic connections is also a documentation issue. They should fix both of these things, but fixing the second one is better than nothing as working documentation would help achieve a privacy-respecting configuration FF derivatives may be more willing to accept as a default. I doubt they will listen to you on the first issue, but now that they've at least acknowledged the documentation issue it may be productive to push them to at least fix that. I will work with tcpdump tonight. Once I know what I'm doing, what's the the most helpful thing to start with? Replicating your tests? Focusing on vanilla FF so I can contribute to the documentation bug report? Focusing on Abrowser since you weren't able to test that one?
