105028 - tabs not in Window menu

Status: RESOLVED EXPIRED

(SeaMonkey :: Tabbed Browser, defect)

Description

[tomk32]

only the active tab is shown in the tasks menu

Comment 1

[R.K.Aa.]

The tabs are displayed at all times. Is there a need to display them in the
tasks menu as well? Sounds like bloat to me. They are quicker to access by
clicking directly than via the tasks menu.

Comment 2

[Alex Vincent [:WeirdAl]]

Actually, there is a legitimate concern here.

window 1 has tabs A & B
  tab A is www.mozilla.org
  tab B is www.mozillazine.org

window 2 has tabs C & D
  tab C is www.mozdev.org
  tab D is home.netscape.com

If you're in window 1 only the currently focused tab of any window will show up.
 That means if tab C is the focused tab in window 2, you can't tell from the
Tasks menu that tab D is even there.

I would confirm this, but I'm not "sufficiently empowered".  Even if invalid,
the behavior is as the reporter describes it for Mozilla 0.9.5 milestone build.
 Seeing this on Win98, recommend OS -> All.

Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.5) Gecko/20011011

Comment 3

[Alex Vincent [:WeirdAl]]

Confirming.  ("sufficiently empowered" now -- thanks Asa!)

Comment 4

[David Hyatt]

Reassigning to new component owner.

Comment 5

[Alfonso Martinez]

*** Bug 136015 has been marked as a duplicate of this bug. ***

Comment 6

[Boris Zbarsky [:bzbarsky]]

There is no "Tasks" menu.  There is a "Window" menu.  Listing tabs in the
"Window" menu would be absolutely incorrect, imo, but a Macintosh person should
comment on that.

Comment 7

[Alex Vincent [:WeirdAl]]

:) At the time, it was called Tasks...

Comment 8

[Matthias Versen [:Matti]]

*** Bug 150296 has been marked as a duplicate of this bug. ***

Comment 9

[jag (Peter Annema)]

-> Future

Comment 10

[Alfonso Martinez]

Changing summary to reflect current menu structure:
tabs not in tasks menu -> tabs not in Window menu

Comment 11

[Alfonso Martinez]

*** Bug 156008 has been marked as a duplicate of this bug. ***

Comment 12

[Jason Bassford]

Suggest creating a dropdown list for any window with tabs (to the right of the
window title entry).  Selecting a tab title in that window's list would switch
focus to the window AND the tab.

Originally I thought it should just be a submenu, but if you have a lot of tabs
open the UI would get very congested if you moused over to the window entry.  A
dropdown list can have a scrollbar and maximum number of items listed at once to
prevent vertical clutter, and it has the added bonus of not displaying the tabs
automatically, but only when the user actively clicks on the down arrow.

Comment 13

[Alfonso Martinez]

*** Bug 163402 has been marked as a duplicate of this bug. ***

Comment 14

[Stefan Borggraefe]

*** Bug 169195 has been marked as a duplicate of this bug. ***

Comment 15

[Mike Calmus]

In addition, the essence of the menu should be reflected in its dock popup under
MacOS X and in external (to the actual Mozilla app) representations of similar
interfaces in other Windowing environments.

Comment 16

[Michael T. Babcock]

Whether they are in tabs or not, the windows are still windows.  We all know
they're windows hooked onto tabs instead of with their own parent frame (Windows
terminology).

They should be listed under the Window menu one way or another (drop downs / in
the main list).  I get very irritated about trying to use tabbed browsing
because of this bug.

Comment 17

[Alex Vincent [:WeirdAl]]

DOM Inspector indicates the menupopup in the browser belongs to an element with
id attribute of windowPopup.  LXR search identifies only four files that match
'id="windowPopup"', and none matching "id='windowPopup'".  One of them is the
new URL field for this bug, at line 54.  (The other three apply to Editor,
Chatzilla, and Mail/News, respectively, so they are unlikely to be responsible.)

Also note bug 109481; the menupopup configurations are nearly identical in terms
of functionality.

Now we know where to look.  What's the right RDF code reference for tabs?

Comment 18

[Boris Zbarsky [:bzbarsky]]

> What's the right RDF code reference for tabs?

You're assuming there is one... to my knowledge, there is not.

Comment 19

[Alex Vincent [:WeirdAl]]

Okay, Plan B.  Is there a specific interface or other object model path
(Components.interfaces.foo.bar.whatever) to get a reference to all open Mozilla
tasks & windows?

If there is and someone can tell me that one, I can script it in.  :)

Comment 20

[Boris Zbarsky [:bzbarsky]]

Windows, yes. The WindowWatcher.

It does not consider tabs to be windows, of course.  Since they are not.

If you want something that enumerates all tabs you're going to have to write it;
nothing exists to do that that I know of.

Comment 21

[Daniel Wang]

*** Bug 195588 has been marked as a duplicate of this bug. ***

Comment 22

[[e-mail]]

In theory you could get the windowwatcher template to generate a submenu for
browser windows, then slap on an event handler to enumerate the tabs for that
window when the submenu opens.

Comment 23

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 24

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420