W3C home > Mailing lists > Public > public-html@w3.org > May 2007


From: Michael A. Puls II <shadow2531@gmail.com>
Date: Fri, 18 May 2007 16:06:31 -0400
Message-ID: <6b9c91b20705181306x28649e90gf7501eda5ed143b5@mail.gmail.com>
To: public-html@w3.org

>From <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-January/009210.html>.

<form action="mailto:" method="get">
    <input name="subject" value="1 2">
    <input type="submit">

When you submit that form in IE or FF (Opera's handling of
action="mailto:" is currently broken. Not sure about Safari),
"mailto:?subject=1+2" will be passed to the mailto client and you will
get 1+2 in the subject field of the mail client's compose window.

In mailto URIs, a + is a +. It is not decoded to a space by mail
clients. So, in order for the value to come out right in the mail
client's subject field, spaces should be encoded as %20 instead.

<http://tools.ietf.org/html/draft-duerst-mailto-bis> is the newest
unofficial mailto URI spec that is supposed to update RFC2368.

Is there a use for encoding spaces as + instead of %20 for action="mailto:"?

If not, I think it should be allowed for browsers to submit spaces as
%20 instead in this case.

doesn't clarify at the moment.

Also, different things happen for post:

<form action="mailto:" method="post">
    <input name="subject" value="1 2">
    <input type="submit">

When you submit that form (in FF for example),
will be passed to the mail client.  This results in "Form Post from
Firefox" as the subject and "subject=1+2" as the body value.

WF2 describes this partially, but what's the use-case for putting the
encoded data set in the body?

There's also this case:

<form action="mailto:?subject=5" method="post">
    <input name="subject" value="1 2">
    <input type="submit">

Since the method is post, subject=5 is not replaced and
is passed to the client. This results in 5 being in the subject field
instead of "Form POST from UA" (For mail clients that support
duplicate hnames at least

There's a little more to the handling with POST. See
"HTMLFormElement.prototype.mailto_createURIFromData" in
<http://shadow2531.com/js/mailto_prototypes1.zip> for an example of
how FF does it with POST. (The TCs in the zip file should be loaded
with JS off to see how the browser normally does it. Try with
Thunderbird latest trunk as the default email clent for example so FF
passes to it.)

In short, if POST for mailto: is going to be defined, there needs to
be a lot more detail in how the mailto URI is generated.

Also, what should happen with other method= values?

<http://www.w3.org/TR/xforms/slice11.html#submit-options> doesn't
really seem to clarify either.

For action="mailto:", not knowing the use-cases for other methods
besides GET, it seems to me that no matter what the method is, it
should work like GET and spaces should be encoded as %20 instead. It
seems to be the only way to make action="mailto:" useful.

Received on Friday, 18 May 2007 20:06:42 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:21 UTC