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

Re: WF2, attach hidden xml

From: Ben Boyle <benjamins.boyle@gmail.com>
Date: Fri, 1 Jun 2007 00:00:15 +1000
Message-ID: <5f37426b0705310700w17d4c992lf0d022d935074f31@mail.gmail.com>
To: "Bruce Boughton" <bruce@bruceboughton.me.uk>
Cc: "Dmitry Turin" <html60@narod.ru>, public-html@w3.org

This sounds a lot like XForms ... is there any guidance on heading
that direction? I have the feeling it's one of the issues with XHTML 2
that's too big a leap from HTML4/XHTML1 ... which is why HTML 5 is
what we're discussing instead?

Just wondering if anyone wishes to clarify the scope around forms? I
quite like what I see in both HTML 5 and XForms but I see HTML 5 being
a reality (in browsers) much sooner...?



On 5/31/07, Bruce Boughton <bruce@bruceboughton.me.uk> wrote:
>
>  Dmitry Turin wrote:
>  I become sure definitively,
> that <input type="hidden" name="a" value="b"> is particular case of
>
> <hidden>
>  <field name="a">b</field>
> <hidden>
>
>
>  While I can see your point, it would be folly to abolish <input
> type="hidden"> in favour of <hidden><field ..></hidden>.  There is nothing
> intrinsically wrong with <input type="hidden"> and it is well entrenched in
> HTML and used on millions of pages.  It would be like me suggesting we
> replace all occurrences of the word "sad" in English with "unhappy".  It is
> not a productive step.
>
>  For your proposal, there seem to be two options:
>
>
> Use a new element, say <hidden>, and keep <input type="hidden"> simple
> name/value pairs
> Use a new element, say <hidden>, and deprecate <input type="hidden">
> Change the specification of <input> so that it is no longer an empty element
> when type="hidden" Option (2) I think is out of the question.  Option (3)
> may not be attractive since <input> is currently defined in HTML4.1 as an
> empty element and I can see nothing in WF2 or HTML5 which states otherwise.
> It would possibly be unintuitive if it were non-empty only for
> type="hidden".  It seems likely, then, that option (1), a new form element
> would be appropriate for this.
>
>  Alternatively, you could have something like the following:
>
>  <html>
> <head>
>   <title>Forms submission with data</title>
>   <data name="mydata">Some JSON/XML data goes in here.</data>
> </head>
> <body>
>   <form>
>     <input type="hidden" name="somedata" source="mydata" />
>     <input type="submit" name="submit" value="Submit data" />
>   </form>
> </body>
> </html>
>
>  The above uses the <label for=""> mechanism to reference the name of an
> element containing the data (possibly in the head to avoid it being
> displayed in legacy browsers--does this work?).
>
>  Bruce
>
>
Received on Thursday, 31 May 2007 14:00:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:15:59 GMT