Now if they could just get around to supporting intermediate CA certificates and all of the Windows certificate stores, not just a couple of randomly chosen ones, that would be swell.
Also, IPv6 support in PAC files would be nice.
If any Mozilla employees come to YC News: Unimportant-seeming stuff like this is why Chrome crushed Firefox in the Enterprise.
This isn't why. At work I deal with two different vendors who refuse to troubleshoot any issues with their products on anything but Chrome. To this day, the issue has never been a browser compatibility issue, but we have to actually temporarily give the user a Chromium-based browser just to get a modicum of decent support these days.
Both vendors, of course, tell us we should just use Chrome because it's the only browser they support. (Even though other browsers work fine.) And unfortunately, most IT staffers end up getting directed by superiors to follow said instructions.
But it was easier to debug on Mozilla so it got supported first because you could eliminate 90% of the bugs before ever having to touch IE.
This is the case now but a decade ago, in the period the original poster was talking about, it was because of things like what they mentioned: Mozilla needed some attention to detail on those tickets, a robust MSI install package, and a polished policy deployment system. Lots of large shops deployed it but it wasn't loved because there was always some wart to work around.