4 ms·
Also happy with my move to Firefox, it surpassed my expectations. Two (small) pain points have been: - customizing userChrome.css .. It was a bit time consumin
by mtone 7y ago
Also happy with my move to Firefox, it surpassed my expectations. Two (small) pain points have been:
- customizing userChrome.css .. It was a bit time consuming to figure out first (I wanted to remove the top bar and use vertical tabs). Happy to be able to do it, but it's not exactly user-friendly.
- Rejection of Windows local certificates store that requires fiddling with a setting to enable. If my certificate store is compromised Firefox is not going to save me. I don't recommend it over Chrome at work since we have one of these for a local server and I'd rather not generate support tickets.
Both of these are not part of Firefox Sync and require manual handling on each PC.
- kbenson 7y agoI just did a little googling, and it appears that Firefox supports group policy settings that can cause it to use system root certs[1], so if it's not working, it may be because the domain administrators haven't bothered to support it. 1: https://github.com/mozilla/policy-templates/blob/f972ec60de7f8a03e9846b3d4840cc01a8f1a8ec/README.md#certificates--importenterpriseroots https://github.com/mozilla/policy-templates/blob/f972ec60de7...
- mtone 7y agoIndeed, but I also count that as a support ticket!
- kbenson 7y agoWell, I would counter that if you want to use a new application (Firefox) with the local server, there should probably be a support ticket to at least ask if they believe it should function correctly. While you probably can assume Firefox will mostly work, there's decades of history saying you probably shouldn't, given the state of enterprise web apps. To be safe, I wouldn't assume Firefox would work any better than lynx for an internal app if neither are listed as supported (and the same goes for every browser).