i just got bit for at least the 3rd or 4th time by
setDefaultFormProcessing(). implementing a cancel button requires that you
set this to false. this is a hard thing to know for a beginning user. or
for me for that matter. ;-) i was wondering what everyone thought about
adding AjaxCancelButton and CancelButton such that they
setDefaultFormProcessing(false). this would be a discoverable and
self-documenting way of dealing with this issue. true, it is
yet-another-class-in-core (or extensions would be fine), but i think it
might be nice.
--
View this message in context:
http://www.nabble.com/cancel-buttons-tp16083133p16083133.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
