Open Bug 109350 Opened 23 years ago Updated 14 years ago

RFE: Add view -> no wrap of text to message view

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: baffoni, Unassigned)

Details

Netscape 4.x had a feature to enable/disable wrapping of text within the currently viewed email (heck, I wish I had that feature in a browser window). I would like to have that functionality in the mozilla browser.
The 4x option only worked on plaintext messages. For HTML messages we use the formatting specified by the HTML/CSS. You can globally change plaintext message settings in Preferences > Mail/Newsgroups > Message Display > Wrap text to fit window width. This is a valid RFE though to put a per-message option in a context menu and/or the view menu as 4x did.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: 4xp
Hardware: PC → All
reassigning to ducarroz.
Assignee: sspitzer → ducarroz
Target Milestone: --- → mozilla1.2
Status: NEW → ASSIGNED
Blocks: 142827
No longer blocks: 142827
I proposed that in bug #160468 as well. We need a checkbox. Being a programmer I found out that setting it to 0 works, but only me, I guess.
Sorry for the above wrong bug... The comment should have gone to bug #145895. And for this bug, I just filled another RFE, see Bug #186732, which is a bit more specific.
Product: Browser → Seamonkey
Assignee: ducarroz → mail
Status: ASSIGNED → NEW
QA Contact: esther
Target Milestone: mozilla1.2alpha → ---
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
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
Group: core-security
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
I've pretty much stopped using Seamonkey for anything except as a HTML editor, so I no longer care much about this bug. However, someone else did vote for this, so if you still use Seamonkey for email, feel free to take up this bug. Thanks.
Reconfirming RFE.
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.