On 7/21/06, Johan Compagner <[EMAIL PROTECTED]> wrote: > I don't know if i like the form submit to be first. > I find it logical that it did go last, It is the Top thing. First all the > children then the parent. (i do find that logical somehow)
I agree with that actually. To me it is more intuitive that a button get's it method called first, even though it is a child of the form. It's also what we deliberately choose for when the button class was created, and how the component is documented. Reversing that logic is very dangerous for clients that may depend on it. > But i don't think it matters to much. Because most have the form.submit OR a > button.submit() implemented. Well, I use both sometimes and actually like the option of being able to have a common piece in onSubmit (e.g. navigation or save), and some specific behavior in the button. Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
