Just a suggestion for Mozilla (the greatest web browser)... It would be cool to have embedded multiple windows... so rather than a window for each instance of Mozilla, have a single window with tabs at the bottom, similar to MS Excel (for want of a better example) Easier said than done imagine... Cheers.

Hi Roger, the MultiZilla project will have this feature. But we need some of those blockers of our back first. We have just started a project on mozdev.org see http://multiZilla.mozdev.org Still a lot of work needs to be done, hey how about helping us a bit? Take a look at http://members.v3space.com/4you2/multiviews/multiviews.html

Make that: http://members.v3space.com/4you2/mozilla/multiviews/multiviews.html

HJ, wanna take this bug then?

Asa, can 'external' projects be assigned into bugzilla? If so, make that a yes!

reassign to H-J.

HJ, if the code is intended to make it into cvs.mozilla.org at some point then a bug here is fine.

Hi guys, I'm helping HJ with this project, as far as I can, but I'm stuck at this moment. Can any of you please give me some advice? I need to know where to locate the source code to prevent ctrl-clicks on links to open a new browser window. Also where can I set window._context.document because I'm getting some sort of error message that it has only a getter. Can I add a setter to it without hurting Mozilla's security in any way or form?? I also add jaggernaut@netscape.com to the cc list as request of HJ. He already helped HJ with some other code for the MultiZilla project, and he is not sure of Peter's 'old' e-mail address. Thank you Neil.

Oops, ctrl-clicking on links opens a new tab already, sorry for the spam.

Ben / Jag / Blake, I'd like to see some progress in this area. What are the chances of changing a few of the mozilla chrome files to get this started in the cvs tree? I see these 3 phases, which do not need to happen all at once. 1) Changing the mozilla chrome files. This will accomodate better the installation of the extra files via XPI for now. 2) Getting the rest of the multiview files checked in 3) Set up the switch from regular view to multi view in prefs. Thoughts?

Totally agree with the need for 1). What type of changes to the moz chrome files did you have in mind? Calls to multizilla script stubs (located in one new js file, replaced when multizilla installed) in strategic places so mtz can hook the necessary events and (perhaps) make dynamic changes to existing XUL instead of changing its source declaration? I havent a clue if this is what you meant or the best way to do it, but its the first thing that occured to me when first playing with mtz. Cheers, Chris

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)

Closing fixed because tabbed browsing is already implemented

eh, this time for real