Closed
Bug 224594
Opened 21 years ago
Closed 21 years ago
mid button click on tab header should always close the tab
Categories
(SeaMonkey :: Tabbed Browser, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 199058
People
(Reporter: dzy, Unassigned)
Details
(Whiteboard: WONTFIX?)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030
with mid button load clipboard url enabled,
mid button click on tab header loads clipboard url instead of closing the tab.
mid button's clipboard url loading should only work when clicked inside a tab,
not on the tab header.
Reproducible: Always
Steps to Reproduce:
1.enable mid button load url
2.mid button click on tab
3.
Actual Results:
the tab loads clipboard url
Expected Results:
the tab closes
Comment 1•21 years ago
|
||
>>Tabbed Browser
The current behavior is what is intended:
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/xpfe/global/resources/content/bindings/tabbrowser.xml#585
Bug 107147 has a discussion of the matter.
The bottom line seems to be that the behavior will remain the same unless a
specific proposal is brought forth to change it.
Component: Browser-General → Tabbed Browser
Comment 2•21 years ago
|
||
I disagree with this proposal. Middle-click should load the clipboard contents
as an URL. IMHO, it should load it in the tab header I click on, or it should
load it in a new tab when I click on the tab bar background. This is not how
it currently works, but it should not under any circumstances kill a tab -
causing potential dataloss. Implementing this proposal would mean that we
have "load URL in tab" behaviour just a pixel away from "kill this tab" which
is just bad UI design. I strongly suggest WONTFIX.
Whiteboard: WONTFIX?
Comment 3•21 years ago
|
||
*** This bug has been marked as a duplicate of 199058 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•