setting browser.navigation.requireUserInteraction to true seems to have fixed it.
Reply on news.ycombinator.com