Anne van Kesteren wrote:
On Wed, 24 Jan 2007 07:02:57 -0500, Elliotte Harold
[EMAIL PROTECTED] wrote:
One would almost get the impression that supporters of XForms-Tiny
would rather write their own spec than engage in dialogue with the
community that created Web Forms 2.0...
Hello, Pot? This
James Graham [EMAIL PROTECTED], 2007-01-24 15:33 +:
Anne van Kesteren wrote:
http://www.w3.org/mid/[EMAIL PROTECTED] (W3C
Member-only)
Anne is it possible to summarise the content of that message? Citing
sources we can't follow up is _really_ irritating :)
I think the following
It would be useful to be able to mark certain submit buttons as
non-validating.
Use case: lots of the forms generated by one of my web-apps have a
Cancel button which simply causes the server to redirect the user back
to wherever they came from. When I use the WF2 extensions to mark
On Wed, 24 Jan 2007 19:03:58 +0100, Martin Atkins [EMAIL PROTECTED]
wrote:
It would be useful to be able to mark certain submit buttons as
non-validating.
Use case: lots of the forms generated by one of my web-apps have a
Cancel button which simply causes the server to redirect the user back
2007/1/24, Martin Atkins:
It would be useful to be able to mark certain submit buttons as
non-validating.
Use case: lots of the forms generated by one of my web-apps have a
Cancel button which simply causes the server to redirect the user back
to wherever they came from. When I use the WF2
On Wed, 24 Jan 2007 20:20:50 +0100, Thomas Broyer [EMAIL PROTECTED]
wrote:
It would be useful to be able to mark certain submit buttons as
non-validating.
Use case: lots of the forms generated by one of my web-apps have a
Cancel button which simply causes the server to redirect the user back
Martin Atkins skrev:
It would be useful to be able to mark certain submit buttons as
non-validating.
Another use case:
The WF2 repetition model allows insertion of e.g. extra rows in a table,
but all inserted rows etc. are based on the same template. If the new
row can be based on different
Hi,
From: Alexey Feldgendler [EMAIL PROTECTED]
However, this doesn't solve the use case of saving an unfinished form
server-side.
Are there any real-world examples where you can save an unfinished form on
the server and continue filling it afterwards, that also has required fields
(when
On Wed, 24 Jan 2007 21:55:16 -, Simon Pieters [EMAIL PROTECTED]
wrote:
However, this doesn't solve the use case of saving an unfinished form
server-side.
Are there any real-world examples where you can save an unfinished form
on the server and continue filling it afterwards, that
