214925 - Character repetition when displaying a mail with URL with password containing surrounding square brackets

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Emmanuel Colin]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030802

When consulting a message with an URL in the mail message body comprising a
password containing surrounding square brackets, the first four surrounded
characters are displayed twice.

Example :
You send ftp://user:[passwd]@foo.bar
You get the following display in the received mail body :
ftp://user:[passpasswd]@foo.bar

This bug was reproduced on windows and linux builds (last was linux build ID
2003080222).

Reproducible: Always

Steps to Reproduce:
1.Open Mozilla Mail
2.Send yourself a mail containing any url of the form
protocol://user:[passwd]@domain.rootdomain (by example ftp://user:[passwd]@foo.bar)
3.Read the received mail


Actual Results:  
The URL displayed in the message body was :

ftp://user:[passpasswd]@foo.bar

Expected Results:  
The URL displayed in the message body should have been :

ftp://user:[passwd]@foo.bar

Comment 1

[Emmanuel Colin]

Attachment: Mail showing the URL display problem

The URL displayed should be ftp://user:[passwd]@foo.bar (like in the mail
source)

Comment 2

[Andreas Kunz]

Comment on attachment 129098 [details]
Mail showing the URL display problem

Changing MIME type to text/plain so Mozilla recognizes it.

Comment 3

[Andreas Kunz]

UGH!
This really happens, also on Windows. Message source is ok, but display is garbled.
It seems to be interpreted as a mail address, a mailto: link is automatically
created on display and that seems to be where the problem happens; the mailto
link is also strange:
mailto:passwd]@foo.bar

I'm quite sure this has already been reported, but confirming now as this is a bug.

Comment 4

[Andreas Kunz]

Ok, did not find another bug about this.
Emmanuel, why did you put it into the MIME component?
To me it seems like an error with linkifying the mail text. I could not find in
lxr where it happens, but most likely in the Mail frontend - MAYBE this is not a
mailnews specific feature at all, but a Gecko one (or something like this).

Comment 5

[Emmanuel Colin]

Andreas, I'm not really acute about components decomposition (first report).
Looking at the components description, that's what looked more likely to me,
since  Mail frontend seemed to be more about widgets/interface than text
content, and, as the bug was obtained introducing some specific character
sequence, I thought it might be a parsing problem.
Feel free to reassign the bug to another component if you feel it a closer match.

Comment 6

[Andreas Kunz]

Yes, parsing. But in another sense...
The actual parsing seems to happen in
netwerk/streamconv/converters/mozTXTToHTMLConv.cpp, so this might - strange as
it sounds - belong to network bugs.
But bug 97835 was filed and fixed by Mozilla developers and also resides under
Mail Frontend, so I'll leave it here for now. 

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420