79128 - In a mailto: URL, we should treat "+" as a space

Status: NEW

(MailNews Core :: Composition, defect)

Description

[[e-mail] (gone - use [e-mail] instead)]

Build ID:  2001050608, Windows 2000, but applies to all platforms.

Summary: In a mailto: URL, we should parse "+" as a space.

Steps to Reproduce:

1.  In the Navigator URL bar, type: mailto:[e-mail]?subject=foo+foo2
2.  Hit Enter (or return on Mac)

Expected Results:

The widget is pre-populated with To: [e-mail], with a subject of "foo
foo2".  (Notice the space, and lack of the "+" character)

Actual Results:

We populate the Addressee and Subject correctly, but we don't replace the "+"
with a space.

Comment 1

[Henri Sivonen (:hsivonen) (temporarily away from Bugzilla)]

Please note, however, that email addresses can contain the character "+".

Comment 2

[Boris 'pi' Piwinger]

I just hit a real world example:
mailto:[e-mail]?cc=[e-mail]&subject=Leserbrief+zum+Artikel+Internationales+Strafgericht%3A+US%2DKongress+droht+Niederlande+mit+Invasion++%28ID%3A+200430%29

My first thought, that everywhere behind the ? we should do it. But as Henri
points out, this might affect addresses like cc above. RfC 1738 says:

   Thus, only alphanumerics, the special characters "$-_.+!*'(),", and
   reserved characters used for their reserved purposes may be used
   unencoded within a URL.

So this means, that bug here should be INVALID, which does make no sense, of
course. Well, mailto does not allow for ?... in RfC 1738 anyways. But RfC 2368 
  does extend mailto ... and AFAICS does not say anything about our problem.

pi

Comment 3

[gekacheka]

The substituting + sign for space does not appear part of general URL encoding
as specified by RFC 1738, as pointed out above.  It is specified by HTML for
form data only:
application/x-www-form-urlencoded 
http://www.w3.org/TR/REC-html40/interact/forms.html#h-17.13.4.1

So it looks to me that (although the plus-for-space substitution would be
convenient) by current standards it does not apply to mailto urls.  Thus, spaces
should be encoded instead as %20 in mailto urls, for example
  mailto:[e-mail]?subject=foo%20foo2  
I agree this bug seems to be INVALID.

Comment 4

[Samuel Sidler (old account; do not CC)]

Stephen, is this bug still valid or can we mark it as invalid?

Comment 5

[Boris 'pi' Piwinger]

I see no reason why it would be invalid. It might have been fixed (I no longer use Mail in SeaMonkey, so I cannot test), but it definitely is valid.

pi

Comment 6

[Stephen Donner [:stephend] Not actively reading bugmail]

A low-priority bug, I'm guessing, but seems to be still valid.

I'll attach a screenshot showing Outlook 2007's lack of compliance/implementation.

I grepped RFC 2368 (from 1998), http://www.ietf.org/rfc/rfc2368, and under section 5. Encoding, it has this to say:

5. Encoding

   RFC 1738 requires that many characters in URLs be encoded. This
   affects the mailto scheme for some common characters that might
   appear in addresses, headers or message contents. One such character
   is space (" ", ASCII hex 20). Note the examples above that use "%20"
   for space in the message body.  Also note that line breaks in the
   body of a message MUST be encoded with "%0D%0A".

A mail developer's opinion would be good, but I can remember vividly this wasn't a big deal at Netscape, since actual space characters in a URL are treated properly...

Comment 7

[Stephen Donner [:stephend] Not actively reading bugmail]

Attachment: Screenshot showing Outlook's non-compliance