Hi Martin,
I agree.
Up to now we only prevent the default behavior in components where this
is really needed, e.g. in fallback components.
Regards
Sven
On 10/30/2014 11:22 AM, Martin Grigorov wrote:
Hi,
Since
https://github.com/apache/wicket/commit/9716f2a7e799133fdf3f7927d0093e6dfe16f529
AjaxFormSubmitBehavior no more allows the default JS event behavior.
The commit message says that the reason is to fix the Ajax Guest Book
example.
In pre 6.x the Guest Book Java code dealt with this itself:
https://github.com/apache/wicket/blame/master/wicket-examples/src/main/java/org/apache/wicket/examples/ajax/builtin/GuestBook.java#L83
This change already caused a problem -
https://issues.apache.org/jira/browse/WICKET-5741
I think Wicket should not prevent the default behavior of the JS event by
default. Each application should decide this for itself.
WDYT ?
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
