218073 - advanced mailto: links work incorrectly

Status: RESOLVED INVALID

(Thunderbird :: Message Compose Window, defect)

Description

[Nathanael Majoros]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Build Identifier: 20030813

Now mailto:[e-mail] seems to work fine. 
But link like mailto:[e-mail];Subject=the_subject with a semicolon will not 
work : it will focus to the Tbird window, but not open a new composer window, 
and of course not fill in the To: or Subject: fields

Reproducible: Always

Steps to Reproduce:
1.Click a link with a more elaborate mailto:[e-mail];subject=my_subject in 
web browser
Actual Results:  
Nothing.

Expected Results:  
start a composer window, possibly fill the to: line if it is somehow parseable, 
possibly the subject line if parseable.

mailto:[e-mail]?subject=blah DOES work
mailto:[e-mail];subject=blah DOES NOT work

Neither are compatible with the  concerned RFC.

Comment 1

[JAV]

It seems bugzilla also doesn't understand how to display these mailto: links. 
Ie. I can't just click the mailto: links. Do you have a webpage with links?

Anyway, I can confirm this is indeed happening with latest Thunderbird.

Comment 2

[gekacheka]

The syntax
  mailto:[e-mail]?subject=blah&cc=[e-mail]
is specified by 
  RFC 2368 The mailto URL scheme

Where is the semicolon syntax specified?
(If not a standard, then I suggest this bug is invalid.)

Comment 3

[Brooks Baughn]

Advanced MailTo: specification such as body= does not reconize %0D%0A so body
test does not show cr/lf in compose mail. The following works in Netscape 4.x
and in IE 4.x, 5.x, 6.x but not in Mozilla 1.4 - Released June 30, 2003.

mailto:[e-mail]?cc=[e-mail]&subject=Corporate Directory:
Reporting Errors&body=Reporting Errors for Corporate Directory Entry (listed
below). The correct information should be (please type the correct information
here):%0D%0A%0D%0A%0D%0A%0D%0AThe Directory displays the following incorrect
information for entry: %0D%0A%0D%0AEmployee # 123456%0D%0ADisplay Name: Last,
First%0D%0ASurname: Last%0D%0AGiven name: First

Comment 4

[Mike Cowperthwaite]

Nathanael Majoros, is there a specification somewhere which uses the semicolon 
to separate fields?  As noted in comment 2, the question-mark *is* in fact 
standard, contrary to your claim in the original report.

Note that Brooks Baughn has opened bug 220099 to deal with the symptom from 
comment 3.

Comment 5

[Mike Cowperthwaite]

No response from reporter; as far as I know, the semicolon is not standard.
=>Invalid