625740 - Compose lockout occurs.

Status: RESOLVED INVALID

(Thunderbird :: Message Compose Window, defect)

Description

[Matt]

Symptoms are basically the same as bug 525359 but occur following the patch to that bug and the message does not contain a contenteditable div.

Email that causes symptoms if included as attachment

Comment 1

[Matt]

Attachment: EML of message causing bug

see if it uploads this time

Comment 2

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #1)
> EML of message causing bug

> Content-Transfer-Encoding: base64
> Content-Type: text/plain; charset="Windows-1252"

Glyph of last line:
with charset=windows-1252:
> Envoyé sans fil par mon terminal mobile BlackBerry sur le réseau de Bell.
with charset=utf-8:
> Envoyé sans fil par mon terminal mobile BlackBerry sur le réseau de Bell.

Charset related issue? Is problem reproduced by next test?
1. view the mail, View/Character Encoding=utf-8
2. Reply, or Forward

Comment 3

[WADA:World Anti-bad-Duping Agency]

Sorry, above glyph was for attachment shown by SeaMoney.
Tb used charset in Content-Type: in .eml file correctly.

WORKSFORME with next build on Win-XP.
> Mozilla/5.0 (Windows NT 5.1; rv:2.0b10pre) Gecko/20110115 Thunderbird/3.3a3pre
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7

Once bug 525359 occurs, any composition by reply/forward doesn't work and same phenomenon as bug 525359 occurs, until some recovery operations are executed(e.g. compose a new message then cancel, restart Tb).
Did you restart Tb after you saw bug 525359 and before you saw problem of this bug with attached mail?

Comment 4

[Matt]

Bug 325359 is supposed to be fixed in 3.1.7.  So a lockout should not occur at all.

The difference here is edit as new does not break the lockout.  The email I posted here is the only instance I have seen at this point, but I found it strange then the OP on GS could not forward with TB, could with blackberry and the lockout occurs.

The only way I can find to break the lockout is to restart Thunderbird.  I did see a post yesterday on GS where the lady suggested that the chat window in face book stopped working once the lockout occurred.

Comment 5

[Jim Porter (:squib)]

(In reply to comment #4)
> Bug 325359 is supposed to be fixed in 3.1.7.  So a lockout should not occur at
> all.

Assuming you mean bug 525359, I'm reasonably sure that is only fixed in 3.3 and hasn't been backported to the 3.1 branch.

Comment 6

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #4)
> The email I posted here is the only instance I have seen at this point,
> but I found it strange then the OP on GS could not forward with TB,
> could with blackberry and the lockout occurs.

> I did see a post yesterday on GS where the lady suggested that the chat
> window in face book stopped working once the lockout occurred.

If bug 525359 by contenteditable=yes in mail is irrelevant to your problem, it may be problem which is relevant to bug 616590.
Patch for bug 525359 and bug 616590 is landed on 3.3 only.

Comment 7

[Mark Banner (:standard8)]

(In reply to comment #5)
> (In reply to comment #4)
> > Bug 325359 is supposed to be fixed in 3.1.7.  So a lockout should not occur at
> > all.
> 
> Assuming you mean bug 525359, I'm reasonably sure that is only fixed in 3.3 and
> hasn't been backported to the 3.1 branch.

That is correct, it hasn't been fixed on the 3.1 branch.

Comment 8

[(no longer active)]

Can a Thunderbird developer please open this email in a debug Thunderbird trunk build and see if it causes any assertions?

Comment 9

[Matt]

closing this bug as it is invalid.

Comment 10

[Matt]

closing this bug as it is invalid.