plain text compose tracking bug

NEW
Unassigned

Status

MailNews Core
Backend
17 years ago
6 years ago

People

(Reporter: blizzard, Unassigned)

Tracking

(Depends on: 3 bugs, {meta})

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
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.
(Reporter)

Updated

17 years ago
Depends on: 92331, 104195
(Reporter)

Comment 1

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

Updated

17 years ago
Depends on: 60419

Updated

17 years ago
Depends on: 64450

Updated

17 years ago
Depends on: 102842

Updated

17 years ago
Target Milestone: --- → M1

Updated

17 years ago
Target Milestone: M1 → Future
(Reporter)

Comment 2

17 years ago
syd, this is a mozilla 1.0 tracking bug - the milestone should be mozilla 1.0. 
Right?
Target Milestone: Future → mozilla1.0

Comment 3

17 years ago
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)
Target Milestone: mozilla1.0 → mozilla1.0.1
A mozilla 1.0 tracking bug makes little sense aimed at some other milestone,
repairing the automated out-pushing.
Keywords: mozilla1.0
Target Milestone: mozilla1.0.1 → mozilla1.0

Updated

17 years ago
Depends on: 67391

Updated

17 years ago
Status: NEW → ASSIGNED

Updated

17 years ago
Depends on: 114429

Comment 5

16 years ago
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.
Target Milestone: mozilla1.0 → mozilla1.2

Updated

16 years ago
Target Milestone: mozilla1.2 → mozilla1.0
Approving this 1.0 tracking bug.

/be
Keywords: mozilla1.0 → mozilla1.0+

Comment 7

16 years ago
minusing in favor of plussing some of the dependencies.
Keywords: mozilla1.0+ → mozilla1.0-

Updated

16 years ago
Depends on: 134439

Comment 8

16 years ago
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.

Comment 9

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

Comment 10

16 years ago
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

Updated

16 years ago
Depends on: 110949, 114954, 137253
OS: Linux → All

Comment 11

16 years ago
Target Milestone is in the past. Do we have a time frame?

pi

Comment 12

16 years ago
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
No longer depends on: 64450

Comment 13

16 years ago
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).

Comment 14

16 years ago
reassign to new placeholder
Assignee: syd → composer
Status: ASSIGNED → NEW

Comment 15

16 years ago
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
Depends on: 144998, 161968
Keywords: mozilla1.0- → meta
Summary: mozilla 1.0 plain text compose tracking bug → plain text compose tracking bug
Target Milestone: mozilla1.0 → ---

Updated

15 years ago
Depends on: 201866

Updated

15 years ago
Depends on: 192905
Product: Browser → Seamonkey
Assignee: composer → nobody
QA Contact: sujay → composer

Comment 16

9 years ago
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
Status: NEW → UNCONFIRMED

Comment 17

9 years ago
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
Group: core-security

Comment 18

9 years ago
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

Comment 19

9 years ago
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

Updated

9 years ago
Group: core-security

Comment 20

9 years ago
It has valid bugs blocking it, so confirming.
Status: UNCONFIRMED → NEW

Comment 21

6 years ago
According to description, this is MailNews bug, moving
Component: Composer → Backend
Product: SeaMonkey → MailNews Core
You need to log in before you can comment on or make changes to this bug.