548724 - Images revert to original size if edited again after being set to a custom size

Status: NEW

(MailNews Core :: Composition, defect)

Description

[[e-mail]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.8) Gecko/20100202 Firefox/3.5.8 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.8) Gecko/20100216 Lightning/1.0b1 Thunderbird/3.0.2

Version 3 of Thunderbird seems to revert images back to original size when those images are edited after being set to a custom size during creation. Version 2.x did not do this and images could be changed without resetting the size, etc.

Reproducible: Always

Steps to Reproduce:
1. Insert/Image
2. Enter location of image file
3. Click on 'Don't use Alternate Text' (this doesn't make a difference to the final outcome, just allows the image to be created.
3. Under 'Dimensions' select 'Custom Size' and enter a smaller size for the image
4. Click OK.
5. Now double click on the image just created.
6. Note that the 'Don't use Alternate Text' has reverted to expecting one. Select it again.
7. On the 'Dimensions' tab note that the custom size has reverted to the original.
8. Click OK.
9. Note that the image changes size back to the original.
Actual Results:  
Image reverted to original size.

Expected Results:  
Image should have stayed at the same size.

No add-ons or themes are active during the test, but it doesn't seem to matter either way.

Comment 1

[Nathan Tuggy (:tuggyne)]

I'm partially able to reproduce this, using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.8) Gecko/20100216 Lightning/1.0b1 Thunderbird/3.0.2 ID:20100216161403 (with a number of extensions installed and active).

The image does not resize to its original dimensions in my case, and a quick look at Insert -> HTML... proves that. However, the dialog does attempt to force alternate text and the original size on the user: one must select Don't use Alternate Text and Custom Size (including the custom dimensions) oneself.

Tentatively moving over to MailNews; I suspect this is a bug in the core code.