if you don't sit in a form then the selection change still works in the browser and we just do a get request (location.href)
If you are in a form then the forms submit is used.

johan


On 3/22/06, Frank Silbermann <[EMAIL PROTECTED]> wrote:

I created a page using a DropDownChoice, overriding the "void wantOnSelectionChangedNotifications ()" to return TRUE.

 

I noticed that it worked, even though I neglected to embed it within an HTML form, adding it simply to the page (and not to a wicket.markup.html.form.Form).  That made me think the component contains its own form.

 

But then, it should also work if I add it to a form – it is, after all, a subclass of FormComponent.  Yet, the HTML specifications seem quite clearly to forbid nested forms!

 

Why is this working?  Does a Wicket FormComponent check to see whether it is contained within a form, generating its own HTML form markup only if not?  Or is the ability to set page parameters and post back something that the embedded _javascript_ can perform even in the absence of an HTML form?


Reply via email to