[
https://issues.apache.org/jira/browse/WICKET-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003319#comment-14003319
]
Sven Meier edited comment on WICKET-5597 at 5/20/14 2:13 PM:
-------------------------------------------------------------
Wicket 7 initializes AjaxRequestAttributes#preventDefault=false, thus the
browser submits the containing form after the Ajax request.
For now you can use type="button" in your markup.
Wicket could do this automatically (as for AjaxButton in WICKET-5594).
But AjaxLink and AjaxSubmitLink know nothing about form buttons currently, so
I'm not sure this is the right solution.
was (Author: svenmeier):
Wicket 7 initializes AjaxRequestAttributes#preventDefault=false, thus the
browser submits the containing form after the Ajax request.
Wicket could do the latter automatically (as for AjaxButton in WICKET-5594),
but AjaxLink and AjaxSubmitLink know nothing about form buttons currently.
For now you can use type="button" in your markup.
> button behaviour changed
> ------------------------
>
> Key: WICKET-5597
> URL: https://issues.apache.org/jira/browse/WICKET-5597
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.0.0-M1
> Environment: tomcat linux
> Reporter: Peter Henderson
> Assignee: Sven Meier
> Attachments: myproject.tar.gz
>
>
> The behaviour of a <button> component with no type="button" attribute has
> changed between 6.15 and 7 M1.
> When the button is connected to an AjaxLink.
> In 6.15 there is no form submit
> In 7 M1 the form is submitted.
> I think the code should control if the form is submitted or not, using
> AjaxSubmitLink or AjaxLink not the markup.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
