496299 - Hotmail sends messages with blank body

Status: RESOLVED INCOMPLETE

(Core :: General, defect)

Description

[u107962]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1pre) Gecko/20090603 SeaMonkey/2.0b1pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1pre) Gecko/20090603 SeaMonkey/2.0b1pre

If I send a message in Hotmail what I type will be sent as blank. It will send. It will go through to the right recipient. The usual Hotmail ad will be at the end of the message. What should be a one line message ends up as three or four blank lines. I tried Internet Explorer and it works okay so this may not be a Hotmail problem. Using recent trunk build on Windows 7 RC.

Reproducible: Always

Steps to Reproduce:
1.Go to Hotmail.
2.Type a message.
3.Send it.
Actual Results:  
Message body replaced with blank lines.

Expected Results:  
Message gets sent.

Comment 1

[lenochod]

Can you try and reproduce with newest SeaMonkey v2.0b1pre?

Can you reproduce in a second profile (see http://kb.mozillazine.org/Profile_Manager) ?

Please try in Safe mode ( http://www.seamonkey-project.org/releases/seamonkey2.0a2/#troubleshooting ).

Comment 2

[Ben]

I can confirm that this bug also exists on Firefox 3.5b4pre version too. This is running on Ubuntu 9.04. All messages sent using hotmail will have a blank message body.

Firefox updated something this morning, but bug is still present. I would also say that in this latest release there seemed to be no text cursor visible in the rich text edit field when creating the message body.

details:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b4pre) Gecko/20090401 Ubuntu/9.04 (jaunty) Shiretoko/3.5b4pre

Ben

Comment 3

[u107962]

New blank profile -- still happens.

New blank profile in safe mode -- still happens.

Note: At first the cursor is as tall as the input box. When you type anything, even a single character, it is normal size. If you backspace it all out it's huge again. Only happens at Hotmail and only in the body of a message. Also, after I sent a message to my Gmail account I replied to it -- still from within Hotmail -- and the usual "On XYZ at XX:XX [e-mail] wrote" or however it goes part went in just fine.

Comment 4

[cee]

Encounter same issue: all seems fine unsing hotmail. Also when clicking the "send" button no errors etc. However when checking the message that has been send it turns out that it has an empty body (subject line is OK). Relevant for several weeks already.

Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2a1pre) Gecko/20090726 Minefield/3.6a1pre (.NET CLR 3.5.30729)

Comment 5

[mac_man2008]

Same issue here: hotmail sends blank messages and also RTF options are disabled.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2pre) Gecko/20090728 Ubuntu/9.04 (jaunty) Firefox/3.5.2pre

Comment 6

[Kenn]

I have the same issue - it started on July 8th 2009.

the problem exists for both firefox and Minefield.

No problem when using IE

Kenn

Comment 7

[mac_man2008]

The problem seems to be solved to me.

I don't know what solved the problem: actually Minefield has been updated very frequently. Now I've got version 3.6a1pre.

What I remember for sure is that after one of those updates I tried to change the text format of a new mail from RTF to simple text and also to HTML and finally I got back to RTF and everything worked properly: no blank mails anymore.

Hope it helps.

Comment 8

[Kenn]

Mac_Man
Tried your work around - no joy whatsoever.

Comment 9

[u107962]

(In reply to comment #7)
> The problem seems to be solved to me.
> 
> I don't know what solved the problem: actually Minefield has been updated very
> frequently. Now I've got version 3.6a1pre.
> 
> What I remember for sure is that after one of those updates I tried to change
> the text format of a new mail from RTF to simple text and also to HTML and
> finally I got back to RTF and everything worked properly: no blank mails
> anymore.
> 
> Hope it helps.

Minefield is the nightly Firefox builds. A new one is automatically created every day whether or not anything has changed. With the auto-updater each one is pushed down in a similar way to security releases.

Can you go back through some previous builds and find an approximate date for when it was fixed (for you at least)? If so, it can greatly help developers figure out what change(s) were involved and identify the root of the bug so it can be fixed in SeaMonkey as well.

Comment 10

[u107962]

Actually, changing the value of general.useragent.extra.seamonkey from SeaMonkey/2.0b1 to Firefox/3.0.12 fixed it for me. So this IS something on M$'s end. This is a tech evangelism bug it seems.

Comment 11

[Kenn]

My user agent for Minefield is already set to Firefox/3.0.12.

This am I tried it again - no joy.

On a hunch i restarted in safe mode with Minefield.  It worked.

Tried both Firefox 3.0.12 and Minefield after that in normal mode and it worked again.

Not sure why that would make a difference.

Kenn

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-CA; rv:1.9.2a2pre) Gecko/20090809 Firefox/3.0.12 - Build ID: 20090809042508

Comment 12

[manolo]

(In reply to comment #10)
> Actually, changing the value of general.useragent.extra.seamonkey from
> SeaMonkey/2.0b1 to Firefox/3.0.12 fixed it for me. So this IS something on M$'s
> end. This is a tech evangelism bug it seems.

(In reply to comment #9)
> (In reply to comment #7)
> > The problem seems to be solved to me.
> > 
> > I don't know what solved the problem: actually Minefield has been updated very
> > frequently. Now I've got version 3.6a1pre.
> > 
> > What I remember for sure is that after one of those updates I tried to change
> > the text format of a new mail from RTF to simple text and also to HTML and
> > finally I got back to RTF and everything worked properly: no blank mails
> > anymore.
> > 
> > Hope it helps.
> 
> Minefield is the nightly Firefox builds. A new one is automatically created
> every day whether or not anything has changed. With the auto-updater each one
> is pushed down in a similar way to security releases.
> 
> Can you go back through some previous builds and find an approximate date for
> when it was fixed (for you at least)? If so, it can greatly help developers
> figure out what change(s) were involved and identify the root of the bug so it
> can be fixed in SeaMonkey as well.

I don't know how to go back through previous builds. Moreover the only thing I did by myself was changing a Minefield parameter in order to be seen as "Firefox <some version>" and not as Shiretoko or Minefield <some version>

Comment 14

[Wayne Mery (:wsmwk)]

Please close the bug WORKSFORME if you no longer see the problem when using a current version.  

Or, if you do see the problem, please comment with details.

Comment 15

[Phoenix]

Resolved per whiteboard