Kathy Brade (brade@netscape.com)
Joaquin Blas (kin@netscape.com)
Joe Francis (jfrancis@netscape.com)
Charles Manske (cmanske@netscape.com)
Michael Judge (mjudge@netscape.com)
Akkana Peck (akkana@netscape.com)
Steve Clark (buster@netscape.com)
Simon Fraser (sfraser@netscape.com)

pensplat

How to reach us:

The newsgroup for discussing Mozilla editor issues is netscape.public.mozilla.editor.
It is gatewayed into the mailing list mozilla-editor; subscribe here (put "subscribe" as the subject of the message).

Design documents for the new editor

The new editor will be based on the new Gecko layout engine, which means that are be rewriting everything, since the old editor was heavily intwined into the old layout engine.

If you're interested in Composer in the old Mozilla codebase (pre-NGlayout); be warned that this code is no longer being developed or maintained, but is still in the tree for those who might want to reference it.

Specs For the New Editor

Please feel free to comment on these specs in the editor newsgroup/mailing list; see the community page for details on how to subscribe.

Known Editor Usability Issues What do we need to fix in order for the editor to be usable for simple daily editing tasks?
Milestones Schedule info: which features do we expect to add in each Mozilla milestone?
Selection spec Selection is part of layout, but the editor team is implementing it
Transaction/Undo Manager A general-purpose set of classes, usable by clients outside the editor too
HTML Typing Rules The rules specifying what happens when the user hits space, return, etc. in various document contexts.
Adding a new method to the Editor Interfaces What files do you need to modify to change one of the nsIEditor interfaces?

UI Specs

These currently describe behavior for 4.x Communicator versions combined with early 5.0 development work. We will update these pages as designs for 5.0 evolve:

Dialog Specs
Table Editing Specs
Editor Widget Requirements

Tools

Editor API Logging

Using the Editor

We are making a major push to get the editor sufficiently functional that people can start using it for their day-to-day tasks. We call this "dogfood", a term you'll hear a lot on mozilla. We have created a list of dogfood issues, and we invite your feedback.