Agreed. Actually, for a proper cancel, I wouldn't even use a button
myself, but just a plain link. The form refactorings I recently did were
driven by requests on this list for people wanting more flexibility in
how forms were processed. In particular, this is true for form level
validation (opposed to field level validation that is supported by
IValidator).
Eelco
Igor Vaynberg wrote:
This functionality is used in a lot more cases then just the cancel button.
Im sure having a CancelButton will help, but it wont eliminate the problem
entirely. Besides people might start subclassing the CancelButton to gain
this functionality and there go good semantics ;)
-Igor
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
