763441 - mailto links don't work with url-encoded non-ASCII characters

Status: RESOLVED WORKSFORME

(Core :: Internationalization, defect)

Description

[Darren Kalck [:D-Kalck]]

Attachment: Test case

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0a1
Build ID: 20120606010119

Steps to reproduce:

Since Firefox 13, click on a mailto link with url-encoded non-ASCII characters


Actual results:

It does nothing


Expected results:

It should an Outlook window

Comment 1

[Darren Kalck [:D-Kalck]]

Seems Firefox doesn't decode the URL when there's url-encoded non-ASCII characters.

Comment 2

[Darren Kalck [:D-Kalck]]

For me no Window opens, for some in the test case, the body is stripped.

Comment 3

[Timvde]

Both links are opened in Thunderbird here, but the first one doesn't have a body.

Comment 4

[April Morone]

(In reply to Darren Kalck [:D-Kalck] from comment #2)
> For me no Window opens, for some in the test case, the body is stripped.

I agree.  It is stripped, as well, for me, of the body.

Comment 5

[Darren Kalck [:D-Kalck]]

After a further research, it seems Firefox treat encoded characters as UTF-8, since %E2%82%AC work but not %80.

Comment 6

[April Morone]

(In reply to Darren Kalck [:D-Kalck] from comment #5)
> After a further research, it seems Firefox treat encoded characters as
> UTF-8, since %E2%82%AC work but not %80.

I agree.  It does seem this way about how Firefox treats encoded characters as UTF-8 in this type of case.

Comment 7

[Darren Kalck [:D-Kalck]]

Could it be related to bug 647403 and the removal of network.standard-url.encode-query-utf8 ?

Comment 8

[Abe - QA (:Abe_LV)]

User Agent 	Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:46.0) Gecko/20100101 Firefox/46.0
Version 	46.0a1
Build ID 	20160112030207
Channel 	nightly

Thank you for taking time to report this.
Are you still able to reproduce this in the latest version ? I cannot reproduce in the current version.

Comment 9

[Abe - QA (:Abe_LV)]

It is not reproducible. Closing this as works for me.
Please feel free to reopen this bug if it still reproduces in the latest versions. Thanks