hey german et al. --is there a ui spec in the works for the spiffy tabbed interface. [currently see it in my debug linux build from last night --woohoo!] hyatt, have any online docs on this that we could link to for further info? just wondering...

The best way to attack this is to: a) develop usage scenarios (cc'ing tpringle,sol) b) determine the lowest hanging fruit in terms of bang for the buck (user benefit for development effort) c) develop one or more ideas and test them d) spec final design I am saying since there is many ways to navigate multiple views in a window and also multiple ways of exposing it to: - context menus (open in new window/open as new tab) - bookmarking (as tab, all open tabs as folder) - session history (one per tab/per window) - type down history (one per tab/per window) - File\ New (in new window/ as new tab) - Open Location (same) - the start page for your browser (as a tab, as a folder, in a window w/o tabs) - what happens when windows are opened from JS (ie the website) - what prefs are needed and exposed to for users (exposing as global on/off or more differentiated) Once we have a good usage scenario we can decide these things fairly quickly. That said I see a great deal of promise in that technology helping users with: - avoiding long window initializion times - supporting visual feedback on new windows opening That said we have a great potential of screwing it up by making it too complicated for and getting in the way of the average Netscape users. I have feeling that if this were to officially go into Mach V we should attempt to keep the initial steps as simple as possible, and by preserving a mode where the naive user will not get confronted with this technology and can maintain a simple one window per URL 'mode'. I am very interested in this and will help drive the UI viewpoint.

German, Why don't you consider MultiZilla as your testcase? This UI is setup by customer demand and not by me. A big plus is that a lot of people like it. Ok, it still needs to be polished a bit, but that seems to count for both mozilla and Netscape too. And please feel free to inform me about any of your dislikes! BTW, isn't this UI spec list is a bit short or brief? And why shouldn't we glue some, or all, ideas from MultiZilla to mozilla, to build a solid and most wanted feature for mozilla? /HJ

to marlon

To comment #1: It would be nice to have prefs for all these things.

Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+, topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword. Please send any questions or feedback about this to adt@netscape.com. You can search for "Moving bugs not scheduled for a project" to quickly delete this bugmail.

nsbeta1, -> 1.0

Approved. Must finish spec for feature to be finished.

Does this really depend on any of the bugs listed above?

notes from design discussions and decisions need to be captured before RTM. QA needs some document for test planning purposes.

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

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