540637 - TB3 has NO word wrap or horizontal scroll in message view

Status: RESOLVED DUPLICATE of bug 538645

(Thunderbird :: Message Reader UI, defect)

Description

[donbaker893]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0

All the current bugs I've looked at refer to difficulties with word wrap in specific instances.  After I downloaded TB 3.0, I lost all access to word wrap in any message view pane, except compose.  Nor is there any horizontal scroll.  Even at full screen, the lines run off the right side, cutting off some of the words.  I have to zoom out to the point where the words and letters are unreadable, "greeked".  TB 3 cuts off words even in "wide view".  I can find no setting in VIEW or TOOLS and Options where the phrase "word wrap" even exists.  It appears that you left it out of this version.  Isn't the point of a mail package the ability to read mail?

Reproducible: Always

Steps to Reproduce:
1. Update from TB 2 to TB 3
2. Open TB 3
3. Click on a message and try to read it
Actual Results:  
(see Details above)

Expected Results:  
automatically made ALL of the words in a line visible in the message pane

Again, it appears that you left a major feature out of TB 3 that existed in TB 2, affecting the essential readability of messages.

Comment 1

[donbaker893]

BTW, I think that horizontal scrolling to read a message would be very annoying.

Comment 2

[Ludovic Hirlimann [:Usul]]

Can you provide a screenshot ?

Do you have extension installed ?

Comment 3

[donbaker893]

I don't think I have the means for a screenshot.  The problem seems to have been resolved in Windows 2000 after downloading and installing V 3.0.1.  (Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1)  Thanks to whoever for fixing it.

Comment 4

[Ludovic Hirlimann [:Usul]]

We used fixed when we know what caused the fix :) Thanks for reporting back.