Currently the view-source window has a menu bar which does not include the "Tasks" menu. This menu is important for switching between windows, so it should be added. Build: 2001070204 Win98

->doron

severity: trivial. yes. needed? maybe.

->rfe and all/all

-> future, trivial, depends though if this is really needed.

Note that MacOS users might be more inclined to use the Tasks menu since they don't have a taskbar.

note that you're confusing issues. mpt is trying to get Window split from Tasks. Mozilla MacOS does have a component bar. ... I think what you really want is a window menu, and on macos once we change to that i will support that for this window (and all others), but that's not the same as a tasks menu. (i'm still uncertain about the need for the tasks menu)

Should you add the Tasks menu (as opposed to the Windows menu) would you mind adding a status bar and the component bar as well?

timeless, i think what skewer was saying is that the view source window lacks a component bar on Mac...

This change would benefit all users, not just Mac users. I can't think of any reason NOT to have a Tasks menu in view-source, if we're going to have a menu bar...

why do we need full browser chrome for the source window? that seems a bit excessive --i don't think we need the toolbars and such. unless having "full browser chrome" doesn't necessarily mean having the Navigation Toolbar and Personal Toolbar there [which would seem excessive here]...? the original rfe to add the Tasks menu should suffice...

well, we don't need the toolbars, but _a_ toolbar w/ find and perhaps some other things might turn out to be useful later. chrome: Tasks/Window, component bar, might as well have security indicator. by the time you have that much you might as well have status text and online indicator. Sidebar is imo still useless, but someone might ask for it. Having a location bar might be useful in the future. [below is really another existing bug report] At some point you end up wanting a browser that renders source, nc4 can be coerced into doing exactly this (i don't remember how, it took a lot of coercion).

timeless, thx for the clarification! i think that just having the Tasks menu and maybe the component bar would suffice here. just my $0.02...

Whoa, whoa, who said anything about full browser chrome? Apparently someone changed the summary for this bug but didn't post a relevant comment identifying themself as the one responsible for the change. Replacing original summary; don't change it back without posting a relevant comment. I am strongly against adding anything more to the view-source window. The menu bar makes sense; nothing else would. The view-source window never accesses the status bar, never has a load time (it should only work with fully loaded pages anyway), does not depend on the state of connected/disconnected, security isn't really important here, and nothing in the location, tool, or personal bar is used. The only chrome in view-source that makes sense is the menu bar, and that menu bar should have a tasks menu. Anything else is a waste of valuable screen space. I'm sorry, but whoever had the brilliant idea of full chrome here struck out...

> never has a load time Not strictly true. It has a layout time (and a parse time) which can be quite appreciable on some pages. 3 seconds on page like http://www.cnn.com on decent hardware is about par for the course. > security isn't really important here Oh, really? I'd prefer to know that I'm getting the source from where I think I'm getting the source. I'd love a security indicator in view source, especially for sites with certs. > The only chrome in view-source that makes sense is the menu bar I've seen a number of people expressing interest in a "browse in source view" mode. This would imply a location bar in view source..... Just tossing out some thoughts. All the above said, I agree that we should keep this bug focused on a Tasks (or better yet Windows) menu.

i have a throbber for viewsource patch in my 9 timezone far tree... seriously, if we ever get linenumbers and jumpToLineNumber, then we can talk about a navigation bar

We should have line:char positioning for errors, I think that should be added too. To do that we'd need a cursor in view-source, though.

This is a bug, not an RFE. On Mac OS, menus shouldn't disappear from the menu bar depending on which window happens to have focus at the time. Non-applicable items should be disabled, but the only difference in the actual content of the menus should be that `View' > `Source' becomes `View' > `Page'.

[offtopic] uses for sidebar: * parse tree (click a non leaf node to select its equivalent in the view source _content) * network errors (click an error to find out what html in the content is associated w/ it) * parse errors (ditto) * javascript errors (ditto)

mass moving open bugs pertaining to view source to pmac@netscape.com as qa contact. to find all bugspam pertaining to this, set your search string to "ItsSharkeysNight".

This hasn't been touched in a while -- Tools and Window are separate menus, now, for one. A "Window" menu is the standard way to change windows on the Mac. Omitting it is like disabling the taskbar on Windows: you have to shuffle windows around to get to one behind the source window. So on Mac at least I'd say it's fairly important.

Since I'm hacking the menu anyways, might as well add window.

So should this be a RFE for All/All to add more functionality to Source View Window or a bug on Mac/All(?) targeted on consistent menubars in all windows(not limited to Source View). I personally would like both. But it does not make it a single issue.

dupe of bug 87514? Is "Window" menu missing on MAC?

(In reply to comment #23) > dupe of bug 87514? IMO, yes, but Mac is not something I use every day. > Is "Window" menu missing on MAC? No.

Will be fixed by my work in 411754.