W3C home > Mailing lists > Public > www-forms@w3.org > August 2002

RE: "Hidden" Input in XHTML

From: Dan Dennedy <DDennedy@digitalbang.com>
Date: Thu, 22 Aug 2002 11:23:39 -0400
Message-ID: <11DC9B322580C843AE5A3D030D950B030315A8@intrabang01.digitalbang.com>
To: "Calbazana, Al" <ACalbazana@epotec.com>, <www-forms@w3.org>

There are 2 sides to a server-side xslt-based processor. The first is
the side that handles all of the XForms Initialization events, sending
resultant xhtml+css+script to the browser. Many notification and
interaction events are handled in the client, but some require http
requests back to the processor. The other side of the xforms processor
handles events that require any instance data manipulation beyond what
the form controls are bound--e.g. submit, insert, and delete or the
setvalue action.

All of my form fields are named based upon the @ref or @bind attribute.
Upon http submission, the processor loads the instances and updates the
submitted instances. The form field name is either an xpath (@ref) or an
id that maps to an xpath (@bind). From that, I can locate the node(s)
and update them, or generate all of the nodes, including the
intermediate ones based upon the location steps of the xpath and the
schema. If it is a submit event, I persist the xml and redirect to
submission action URI. Otherwise, I run initialization events to
recreate the xhtml form.

So, you see, there is no need for explicit hidden fields for data
retention. However, I do have to maintain an xhtml hidden field that
contains a list of pending insert, update, and setvalue actions prior to
a submit event.

-----Original Message-----
From: Calbazana, Al [mailto:ACalbazana@epotec.com] 
Sent: Thursday, August 22, 2002 9:50 AM
To: 'www-forms@w3.org'
Subject: "Hidden" Input in XHTML

I've read the previous posts regarding "hidden" inputs with respect to
XForms.  The suggested approach is to leave the instance data unbound
and push the model through to the processor creating the effect of a
hidden field.  Not sure how this would work in an XForms XSLT though.
Since the "model" is not coming back in the form of an XML document, how
might the model HTMLify hidden input fields?  
I guess I could create an extended control that contains a reference to
the model element or create some funky template to create hidden form
fields using XSLT/XPath functions.  I guess this is more of an XSLT
exercise than anything, but any help would be appreciated.

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

Received on Thursday, 22 August 2002 11:24:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:06 UTC