183238 - Proposed middle mouse behavior with tab navigation

Status: RESOLVED DUPLICATE of bug 59132

(SeaMonkey :: Tabbed Browser, enhancement)

Description

[Mauricio Silveira]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020605
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020605

Let's just think a little about the middle-mouse click behavior with tabs and 
navigation:

1.) Middle-click on current page's body may be annoying when you wanted to
middle-click the LINK to open a new tab/window and what you get is the url on
the clipboard to be loaded on that tab(in cas it is valid). I know the latter is
a feature.
2.) If middle-click is meant to paste stuff on *nix, why should it be natural to
perform a close on the tab?
3.) The `X' on each tab should help.

So, my ideas about tab navigation and middle-click behavior is that things
should be like this:
1.) A single middle-click over a tab should paste the url in case
middlemouse.contentLoadURL == true ; Shouldn't a double middle-click be added
for closing the tab in this case? And case middlemouse.contentLoadURL == false,
shouldn't both single middle-click and double middle-click close the tab?
2.) Middle-click over the tab bar with an url in the clipboard should open the
url in A NEW TAB.
3.) Shouldn't specific "current page middle click for new URL", the middle-click
over the page's body have a user_pref statement for the sake of
enabling/disabling it?(I would disable it, i usually missclick urls i want in a
new tab :).

This is what i may name a "perfect behavior" for middle-click.

You know, i'm using mozilla 1.0, whenever any of theses proposals became true in
new releases, sorry, but i want to upgrade to mozilla 1.0.1 as soon as i prepare
a good .spec for a rpm package, i don't mean to use unstable mozilla releases
for a while.

Would like to read comments about this

-MS

Reproducible: Always

Steps to Reproduce:

Comment 1

[R.K.Aa.]

I consider what you suggest here as the *least* desireable behaviour thinkable.

The clue is "contentLoadURL":
The tab itself *IS NOT CONTENT AREA*. It should NOT be possible to "paste-load"
anything there. As little as it should be possible on scrollbars or other parts
of the user interface. Middle-click to load a page should only work if you use
it on the CONTENT area - or the urlbar itself.

You write "If middle-click is meant to paste stuff on *nix, why should it be
natural to perform a close on the tab?"

Middle click is not supposed to paste "stuff" absolutely everywhere on *nix.
It is not supposed to paste on tabs or scrollbars, for instance. IThat would be
completely wrong.

The bug about consistant behaviour of the middle click and modifiers is bug
59132 resolving as dup.

*** This bug has been marked as a duplicate of 59132 ***