- From: Christian Schmidt <whatwg.org@chsc.dk>
- Date: Wed, 24 Jan 2007 22:37:55 +0100
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
Received on Wednesday, 24 January 2007 13:37:55 UTC