This is a mozilla 1.0 plain text mail composition tracking bug. It's for tracking problems that are in plain text mail compose that are critical for a mozilla 1.0 release.

Bug 108120 is a mozilla 1.0 tracking bug for text editor bugs as well.

syd, this is a mozilla 1.0 tracking bug - the milestone should be mozilla 1.0. Right?

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)

A mozilla 1.0 tracking bug makes little sense aimed at some other milestone, repairing the automated out-pushing.

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.

Approving this 1.0 tracking bug. /be

minusing in favor of plussing some of the dependencies.

Bug 134439 was just filed requesting that plaintext compose change from its current "wysiwyg wrapping but sometimes you get stuck in non-wrapping replies" mode to the old 4.x "editing replies is the same as any other text but everything wraps to window width instead of where the sent message will wrap". I cc'ed people I thought were interested; mentioning it here in case I missed someone.

Please update this bug with an [adt1] - [adt3] impact rating (or take it off the list if it doesn't even rate adt3.) Thanks!

Is there a reason for OS=Linux? Suggestions to add: bug 110949 (Edit draft destoys quotes) bug 114954 (Mail editor misinterprets quote prefixes in pasted text) bug 137253 (Rewrap: Don't touch long words) pi

Target Milestone is in the past. Do we have a time frame? pi

This bug is assigned so I am not doing it myself, but suggest: Change summary to: plain text compose tracking bug Remove target milestone. Remove obsolete keyword. Add meta keyword. Remove resolved bugs? I do remove bug 64450 which has nothing to do with this here anyways. pi

Provided the "1.0" is dropped from the bug sdescription, I am nominating bug 155622 - Wrapping information lost on "Edit as new", "Edit draft" (RFC 2646 format=flowed).

reassign to new placeholder

Since nobody has an opinion I apply the changes from comment 12. I do not delete closed bugs from dependency. Should we? Adding bug 144998, bug 161968. pi

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

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

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

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

It has valid bugs blocking it, so confirming.

According to description, this is MailNews bug, moving