Closed Bug 214849 Opened 21 years ago Closed 21 years ago

Background-image is not converted to CID

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows ME
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 116867

People

(Reporter: ronkillmer1, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5b) Gecko/20030729 Mozilla Firebird/0.6.1
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5b) Gecko/20030723 Mozilla Thunerbirs/0.1

When using Format|Page Colors & Background to set custom background, the
resulting inline CSS within the body tag of background-image: url(file:///E:/my
documents/image.gif) is not being processed by the binary encoder not being
updated to a CID when the message is sent.

Inserting images else where in a message does get handled correctly where the
encodec binary is embedded in the message and the sorce ref is the CID of the
specific image.

Reproducible: Always

Steps to Reproduce:
1.Ref in details
2.
3.



Expected Results:  
The file url should have been replaced with a message CID pointing to the
uuencoded embedded binary data.
background images  as in-line content is a basic
ingredient for most stationary newsgroups.
This is a regression, as background images were
possible in previous builds
JoeS
The OS is in error and should be Windows ME, though other Win32 OS are also
reporting this bug in NG secnews.netscape.com/netscape.test.multimedia.

Bug first appeared when TB was switched from using the background property of
the body tag to the CSS attribute of background-image: url( )

I almost decided to class this bug as severity of Blocker since it does block
testing of the CSS abilities of TB to generate multimedia stationery messages.

Also related is a fault of TB to do Message|Edit as New where a background-image
attribute is contained in a boty tags inline CSS.  The edit strips the
background-image when the scource is viewed of the message in the compose window.
OS: Mac System 9.x → Windows ME
I'm confused. Isn't this the very issue I told you guys I was working on in the
forums? i.e. Bug #116867. I could have sworn we have a thread talking about this
bug.

*** This bug has been marked as a duplicate of 116867 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
This bug was filed prior to the thread in Mozillazine.

I did a search and from my keyword selection no relavant related bugs came up.
From the age of the #116867 bug I sure didn't get the right words to find it.

From your comments in the other bug I say your a very talented fellow.

Thanks for digging through and getting a handle on the causes.
cool...hopefully my patch fixes this for everyone.
You need to log in before you can comment on or make changes to this bug.