Thank you for correcting me, I should have said "properly multithreaded or multiprocessing browser like IE or Chrome". Since a properly designed multithreaded applications shouldn't suffer from UI non-responsiveness as badly as FF does. Of course separating the user interface process from the content processes also would have fixed this issue.

I'm glad to hear the electrolysis project has been rebooted. That plus a working silent update( see bug #711475 ) would go a long way to making Firefox relevant again.