The first alternate browser I went to after I ditched Internet Explorer (back in my Win98 days) was Opera. I stayed with Opera for several years until I discovered an annoying graphic memory leak that causes the entire Windows OS to eventually display everything in 2-bit color. In other words over a course of time, Windows color depth would actually be reduced from 32/24, to 16, to 8 and eventually 2 bit color. This would effect every program and graphic function across the board with only one exception, Print Screen. Long story short, I traced the cause back to Opera after weeks of testing and had the bug confirmed by two other users.
However, Opera developers had their head up their ass and no amount of log files or convincing would get them to look into that bug other than the retarded response of "reboot your computer."
So I went to KDE (when I moved to Linux) for about a year. KDE is fine for quick browses but the more than a few pages didn't render properly. I needed a more serious browser with better rendering
So I ditched that crap and moved to Firefox and all was good....
Until sometime around 2007 or so when the hideous
sec_error_reused_issuer_and_serial page reared its ugly head. Back then, the
intentional bug was tolerable since it was a single click to gain access to the problematic site. But as new patches progressed, the procedure became more and more convoluted. Until this year when the last few FF updates actually forces the user to go through their certificates, delete them, go into another window to forcefully accept said certificate
then go back to the questionable site to accept the defective certificate.
Users on the FF forum complained. One thread ran from 2007 to 2009 until a moderator closed it. FF dev solution? Contact the owner or manufacturer to update the certificate. That would be fine and dandy if the manufacturers still support their hardware. The FF developers absolutely refuse to budge on this issue.
Today I've just about had it. The sec_error_reused_issuer_and_serial problem is forcing my hand and I'm ready to say ---fudgesicle--- you, suck a whores

, eat dog ---steaming pile of meadow muffin--- and goodbye to Firefox. Without a workable solution that doesn't
require 17 steps to force acceptance of "questionable" certificates, Firefox is not worth the effort anymore.
There is no browser war. It's just a bunch of lame ducks swimming around in a pond and the hunter has to make a pick between crap and crap.
So what's the next browser?