W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2006

[whatwg] Forms and POST'ing to data: URL's

From: Ian Hickson <ian@hixie.ch>
Date: Sat, 26 Aug 2006 00:28:12 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0608260026320.10139@dhalsim.dreamhost.com>
On Thu, 24 Aug 2006, Charles Iliya Krempeaux wrote:
> 
> One use case, from my point-of-view, was to allow for non-networked form 
> submits

The solution is to use a scripting language, IMHO.


> What really motivated me to think about it is that is that I was writing 
> a blog post about how to create HTML e-mail signatures with hCards built 
> into them.
> 
> I wanted to include a form to help them do this.  The reader would fill 
> in their name, e-mail address, etc, and it would generate HTML code they 
> could use for their HTML e-mail signature.
> 
> However, I didn't want the form to make a request back to my server. 
> (Because people could be reading this in their feed reader were they 
> have the blog post cached from my feed.)  I wanted it to be entirely 
> self contained within the blog post.
> 
> So, as you mentioned, one solution is JavaScript.  However, JavaScript 
> has a couple problem.  #1: It complex.  (Yes... I'm lazy :-)  )  #2: Not 
> all blog readers will allow the execution of JavaScript.

Not all readers will allow form submission, or data: URIs, either.

It seems that you'd very quickly run against limitations of a templating 
solution, and that the complexity of such a solution isn't worth the 
limited use it would get.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 25 August 2006 17:28:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:28 UTC