User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 There is currently no event for double-clicking a browser tab. bug #158040 requests "close on double-click", whild I would request that a double-click reloads (specifically focuses, then reloads) the tab. Reproducible: Always Steps to Reproduce: double-click on any open browser tab Actual Results: nothing Expected Results: A user-definable action, configured in Preferences -> Tabbed Browsing. Nothing, Reload Tab, New Tab, or Close Tab are the recommended options. Default to "nothing" (using default theme) Any double-click action will first focus the tab (preserving current feel) then perform the action. (that specific sequence events for closing a tab spawned a discussion and caused bug #158040 to be closed "won't fix", this request is for a user definable action)
linking to related bug
Bug 157849 is also a WONTFIX
ick, I didn't realize that middle-click would close the tab, that's certainly something that could be user-settable let me ammend my feature request: double-click and middle-click should both be customizable to make a case for all of these features: any GUI enhancement that reduces mouse movement improves accessability (for those with reduced range of motion and/or control) and usability (allowing more rapid execution of specific, commonly performed tasks)
Confirmed, this is an RFE. Bug I doubt it will ever be made. If you want it, check mozdev.org for a project, or start a new project. I'm only confirming this because it's an RFE, but I suggest resolving it as WONTFIX. Check out bug 158040.
I find it inconsistant that bug #158040 was "wontfix" but somehow closing a tab got assigned to middle-click, when there is both a button and a keyboard shortcut for that function (which appears to be the reason bug #157849 was "wontfix") I also see how double-click can be accidently activated and agree that the user *shouldn't* assign it to any destructive action, but then again middle-click seems to have two opposing uses: middle click a link to create a new window/tab, or middle click a tab to destroy (where a distance of a few mm could be the difference) It makes sense to me to either reconcile this disparity or allow the user to customize the behavior (even if only in a conf file). thanks for pointing out mozdev, it seems multizilla is the best candidate for this feature
I would like to change the summary to: [RFE] double-click/middle-click on tab to reload page and switch the product to Firefox. Any objections? Or should I create a new bug?
I think that double-clicking a tab should have same effect as double-clicking tab bar. Same goes for middle-click.