content: Uhhhh... 1/2 assed merger into Chrome. Failfox has random lag spikes on flash content (and cpu usage doesn't show any spikes). I tried the 64 bit version of Failfox. I promptly swapped back to 32 bit because things were broken that weren't broken on 32 bit. I turn automatic updates on both Chromium and Failfox because I'm tired of new random features and things working then not working because someone has decided to wage their own personal e-penis war on Flash or some other added worthless feature (like removing click to play because....?). Failfox features I never wanted list quite high. I'm rather glad I managed to customize the one I have to run on a machine with 4 GB of RAM (back when it had 1 GB, gotta love ancient backup systems right?). It's 2017 and I am once again loading multiple web browsers because both render the same content differently (Failfox happens to render it like ass, all jaggy and whatnot), while Chromium runs it smoothly and makes it look smooth. Well, until they decided I should not have any say about how plugins I install should be ran. This shit sucks. I don't think forking these projects is the answer. Nuking them both after shoving said nukes up the developers asses maybe. But no fork. Just make something else.