Re: [whatwg] Comparison of XForms-Tiny and WF2
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 is Kettle. You're black. 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 :) -- Eternity's a terrible thought. I mean, where's it all going to end? -- Tom Stoppard, Rosencrantz and Guildenstern are Dead
Re: [whatwg] Comparison of XForms-Tiny and WF2
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 archived message is a copy of the same one that Anne cites - http://lists.w3.org/Archives/Public/www-forms-editor/2003Sep/0006.html :wq --Mike smime.p7s Description: S/MIME cryptographic signature
[whatwg] WF2: Non-validating submit buttons
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 required fields, formats, etc the Cancel button won't submit until the form is completed correctly. This doesn't make much sense from a UI perspective. I propose a flag on the submit button elements (both INPUT and BUTTON TYPE=SUBMIT) which causes the browser not to run the usual validation procedure before submitting when that button is pressed. For example: input type=submit validate=no / I'm not fussed about the exact name/usage of the attribute, but it seems like a common enough case to warrant a declarative solution rather than a script one.
Re: [whatwg] WF2: Non-validating submit buttons
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 to wherever they came from. When I use the WF2 extensions to mark required fields, formats, etc the Cancel button won't submit until the form is completed correctly. This doesn't make much sense from a UI perspective. I second that. Antoher use case is saving an unfinished form on the server so that the user can continue filling it later. -- Alexey Feldgendler [EMAIL PROTECTED] [ICQ: 115226275] http://feldgendler.livejournal.com
Re: [whatwg] WF2: Non-validating submit buttons
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 extensions to mark required fields, formats, etc the Cancel button won't submit until the form is completed correctly. This doesn't make much sense from a UI perspective. Cannot you accomplish that by using two forms? form id=cancel action=/cgi-bin/script method=post/form form action=/cgi-bin/script method=post pName : input name=name required/p pinput type=submit name=ok value=Save input type=submit name=cancel value=Cancel form=cancel/p /form -- Thomas Broyer
Re: [whatwg] WF2: Non-validating submit buttons
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 to wherever they came from. When I use the WF2 extensions to mark required fields, formats, etc the Cancel button won't submit until the form is completed correctly. This doesn't make much sense from a UI perspective. Cannot you accomplish that by using two forms? Actually, the Cancel button could easily be just a link, not a submit control. However, this doesn't solve the use case of saving an unfinished form server-side. -- Alexey Feldgendler [EMAIL PROTECTED] [ICQ: 115226275] http://feldgendler.livejournal.com
Re: [whatwg] WF2: Non-validating submit buttons
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 templates, a server round-trip is often preferred (one can probably achieve the intended effect using Ajax, but sometimes a more low-tech solution is preferable). One example of this is this a select control where the user can choose an element to insert and a submit button that inserts the selected element using a post-back but without validating fields on the page that has not been filled out yet: +- New paragraph ---+ | Select paragraph type:| | [ Text paragraph |V]| | [ Insert paragraph ] | +---+ Yet another use case: A web application allows a user to order e.g. an insurance. The price depends on a lot of things, and not all calculation and user validation can be done client-side. Before ordering, the user may want to select different product options and calculate a price before making the actual order. In this case, the specified options are sent to the server for calculation, but the other fields are just silent passengers on the round-trip, so that the fields keep their values after the post-back. This also applies in e.g. a CMS where the user fills out a template and is able to get a preview using a post-back. It would be convenient to allow previews even though not all required data has been entered yet. Christian
Re: [whatwg] WF2: Non-validating submit buttons
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 the form is finished)? I have never seen such a form. Regards, Simon Pieters _ Tjäna pengar - sälj på auktion http://tradera.msn.se/
Re: [whatwg] WF2: Non-validating submit buttons
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 also has required fields (when the form is finished)? I have never seen such a form. Saving incomplete forms is a recommendation in cite isbn=0-7357-1410-X ;) Devensive Design for the Web/cite which provides www.bankone.com as an example site that saves incomplete applicatios (I don't know however if that's via save button or just up to the last completed step). IMHO non-validating button makes sense for saving drafts of various kinds (webmail, blog post, wiki page). Another use-case is a preview button. Example: comment submission on a blog. You may require users to fill-in their name and e-mail address, but these fields aren't neccessary to display a preview of text formatting. -- regards, Kornel Lesiński
