This bug seems to have existed in Firefox for nine years. (See Bugzilla.) According to Alain Knaff on the Bugzilla thread:
What happens is that Firefox for some weird reason does not get the mouse position directly from the button-release event, but instead prefers to request it separately. Under high-load condition, this means that the mouse may have moved since button release, and Firefox wrongly interprets that as a drag.
People seem to suspect that this happens on slower computers, when Firefox is under heavy load, or when other processes are taking up resources.
I first found the thread above more than a year ago, when the only solution on offer was a Firefox plugin that no longer worked.
Having had tabs tear off three times in a day recently I searched again for a solution, and had a sense of deja vu when I found the same thread.
However, I'm happy to say that there is now a solution posted on the thread:
Type about:config into the address bar in Firefox and look for
browser.tabs.allowTabDetach
Double click to change from true to false.
No comments:
Post a Comment