Open Bug 169691 Opened 23 years ago Updated 4 months ago

toggle line wrap on/off for current composition in plain text

Categories

(MailNews Core :: Composition, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: mozilla, Unassigned)

References

(Blocks 1 open bug, )

Details

A very handy feature of NN4 was that, when composing a message, you could go to View -> Wrap Long Lines and turn off wrapping for the current composition window. This is needed when composing a message with long file paths, or other such strings. Currently Mozilla gives no way to turn off wrapping for the current composition without going into preferences before and after composition.
4xp
Keywords: 4xp
-->varada
Assignee: ducarroz → varada
taking all of varada's bugs.
Assignee: varada → sspitzer
Just filled a RFE, see Bug #186732, as this is not a bug in the strict sense. It just need improvement.
Severity: normal → enhancement
OS: Windows XP → All
Hardware: PC → All
Product: MailNews → Core
*** Bug 271284 has been marked as a duplicate of this bug. ***
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Filter on "Nobody_NScomTLD_20080620"
QA Contact: esther → composition
Product: Core → MailNews Core
Severity: normal → S3
Summary: No way to turn off wrap for current composition → toggle line wrap on/off for current composition

assuming this is for plain text composition

Summary: toggle line wrap on/off for current composition → toggle line wrap on/off for current composition in plain text
See Also: → 512051

💡 idea

If this (toggling line wrap on/off) is implemented as a toolbar button, it would have the additional benefit of being able to control the line wrapping of either the entire message or only a selected paragraph:

  • if text is selected: button toggles line wrap only for the selection (this is bug 1139059).
  • if no text is selected: button toggles line wrap for entire message
See Also: → 1139059
You need to log in before you can comment on or make changes to this bug.