I returned to Firefox from Chrome about 1 year ago due to nagging rendering bugs with linux. Running out of video memory triggered a bug where Chrome would leave a stale buffer of the window on screen. My inputs still got to browser, I could change tabs, scroll, go full-screen it just won't repaint the window. I would have to restart my window manager to get it to repaint. The only solution was to disable GPU rendering but then scrolling was terrible. I know I was pushing the limits of my 7 year old Thinkpad, but I liked my keyboard and 3 real mouse buttons. I moved to Firefox and even with GPU rendering enabled never had that problem.
Months later that Thinkpad's battery died and I moved to working on a modern dual monitor desktop machine. Thinking my problems with Chrome would be gone with plenty of horsepower I discovered a new bug. My monitors are (unfortunately) BGR pixel order not much much more common RGB. It's pretty easy to setup in Cinnamon/Gnome just change 1 dconf key and font rendering is great. Chrome completely ignores this setting and renders fuzzy haloed fonts, plus it not just for Linux, Chrome does the same under Windows. The best workaround is to enable grayscale sub-pixel rendering in chrome://flags but fonts are still fuzzy. From what I found while debugging the problem Chrome used to support different pixel orders but broke it recently.
Once again Firefox renders fonts just fine by reading the pixel order set by the OS. Chrome isn't alone in the pixel order problems, Sublime Text and Atom both suffer from the same problem.