316676 - URL in plaintext messages is treated as HTML

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking, defect)

Description

[Christian Schmidt]

URL's in plaintext messages are somehow treated as HTML, i.e. they are HTML-decoded when you click on them or when you select "Copy link location" from the context menu.

Steps to reproduce:
1. Send a plaintext message (i.e. not a HTML mail) containing the following URL in the body: http://example.org/?foo&#65
2. In you sent folder, click on the link

Expected results:
The default browser should open http://example.org/?foo&#65

Actual results:
The default browser opens http://example.org/?fooA
It appears that the HTML entity (with a missing semicolon) "&#65" is translated to "A".

The same also occurs when using "Copy link location". The URL is displayed as intented, though.

Comment 1

[Ray Booysen]

Christian, what version of thunderbird are you using?

WFM
Windows XP
1.6a1 (20051108)

Comment 2

[Christian Schmidt]

I'm using a recent trunk build: 1.6a1 (20051115)

Comment 3

[Ray Booysen]

OK, I upgraded to 20051109 and still don't see it.
So at least we have a small regression window in the case of a bug.
Between 20051110 AND 20051115


Here are the checkins via Bonzai for this period.
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=ThunderbirdTinderbox&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-11-10&maxdate=2005-11-15&cvsroot=%2Fcvsroot

Comment 4

[Christian Schmidt]

I also saw this in 1.5 beta.

Comment 5

[Magnus Melin [:mkmelin]]

Seeing this on Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051112 Thunderbird/1.5 ID:2005111204

Yep, auto linking has resolved the Numeric Character Reference in the URL to it's corresponding character.

On the other hand, I doubt such an URL really makes sence in the real world...

Comment 6

[Christian Schmidt]

> On the other hand, I doubt such an URL really makes sence in the real world...
The real-world example that I encountered contained "&copy=...". That's probably not an unlikely case.

Comment 7

[:Gavin Sharp [email: [e-mail]]]

In that range, bug 312760 stands out as a possible cause.

Comment 8

[Mike Cowperthwaite]

Reproduced with TB 2a1-0604, Seamonkey 1.5a-0518.

Comment 9

[Magnus Melin [:mkmelin]]

I think bug 315927 might also be a candidate for causing this, given the range in comment 3. Maybe...

Comment 10

[Magnus Melin [:mkmelin]]

This is no longer an issue on trunk.
->WFM