Gili wrote:
On Wed, 02 Mar 2005 22:43:27 +0100, Martijn Dashorst wrote:
You're saying that if a user commits something to the database, then
hits back, enter different data and "submit" again it should add the
new data but not undo the original commit? I understand some websites
let you do that, but I would argue that the behavior I suggested is the
correct and intuitive one. Back means undo to me in all cases I can
think of.
Can you come up with a clearer use-case where it does not?
Select an object from list, edit object in seperate page, save (which
stays on this page), hit back twice, select other object, edit that
other object.
I *definetely* don't want my saved object be rolled back ;-)
Martijn
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
