Closed Bug 684357 Opened 15 years ago Closed 15 years ago

image resizing in mailnews

Categories

(SeaMonkey :: MailNews: Message Display, defect)

SeaMonkey 2.3 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

(seamonkey2.3 affected)

RESOLVED DUPLICATE of bug 534083
Tracking Status
seamonkey2.3 --- affected

People

(Reporter: ronaldrosenthal, Unassigned)

Details

(Whiteboard: [2.1-unaffected][2.2-affected])

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 Build ID: 20110830151746 Steps to reproduce: received email with .jpgs viewed them Actual results: they do not resize. version 2.1 does, 2.2 does not, 2.3 does not, 2.3.2 does not Expected results: image should resize if it is larger than the open window in mailnews checked about config, and image resizing in mail news is set to true similar to 2.3 bug I submitted. again, reinstalled 2.1 and it works fine in that version
For reference: Your other Bug 682163 - images do not resize in mail. Could you explain the difference between these two bugs? (Kind of escaping me as I'm not familiar with Mail. One is an automatic & the other a manual resize?) In any case, one or both may be a DUP of Bug 534083 - Provide image scaling for embedded images?
I input 682163 a few weeks ago. I had reverted to Seamonkey 2.1 before that because the auto image scaling had quit in newer versions. both the auto and manual image scaling do not work since 2.1. I like the feature and will revert to 2.1 until the auto update feature indicates a new version is available. so I will update this bug as necessary. IMHO, this one needs to be fixed, as it has been showing up periodically, then getting fixed, then showing up again.
Wayne, do you see this on Thunderbird (5.0 or later)?
Component: General → MailNews: Message Display
QA Contact: general → message-display
Whiteboard: [2.1-unaffected][2.2-affected]
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.