125586 - bad parse of mailto url containing "% escaped" (?) characters

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking, defect)

Description

[Craig Reynolds]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205
BuildID:    20020205

This page (http://newsseer.com/) contains a mailto link labeled
"Feedback" which is created by JavaScript.  When hovering over the
link, the URL is displayed (on the bottom line of the browser window)
as "mailto:[e-mail]?subject=NewsSeer feedback" but if I
mouse right and Copy Link Address it contains "% escaped" characters
(what are those called?) like this:

mailto:%66%65ed%62a%63%6b%40newss%65%65%72%2e%63o%6d?subject=NewsSeer%20feedback

Apparently this causes the parsing of the mailto to go awry.

Reproducible: Always
Steps to Reproduce:
1. go to http://newsseer.com/
2. click on "Feedback"


Actual Results:  The mail composition window that comes up looks like this:

    To: [e-mail]?subject=NewsSeer
    To: feedba
    Subject: NewsSeer feedback


Expected Results:  instead of:

    To: [e-mail]
    Subject: NewsSeer feedback


I hope this is not a duplicate, it seems like it might be related to:

Bugzilla Bug 125080
mailto url with raw non-ASCII subject and mail body is not working
http://bugzilla.mozilla.org/show_bug.cgi?id=125080

Comment 1

[timeless]

neat

Comment 2

[Kai Lahmann (is there, where MNG is)]

confirmed

Comment 3

[Boris Zbarsky [:bzbarsky]]

This is not an XP apps thing... over to mailnews:networking where they do the
URI parsing.

Comment 4

[Ian Nartowicz]

This seems to work OK for me in 1.1 alpha.  Has it been fixed?

Comment 5

[Olav Vitters]

Also WFM in 2002-08-30-05 Linux

marking as such

Comment 6

[Craig Reynolds]

At the risk of being redundant, it also works for me (the original whiner)
in release 1.1.  I gather it just "went away" as result of changes
elsewhere?  In any case, thanks for your help.

(Oddly, today when I went to http://newsseer.com/ to test this with my new
Mozilla 1.1, I found a completely unrelated problem with that page which
I just reported: http://bugzilla.mozilla.org/show_bug.cgi?id=168062)