[
https://issues.apache.org/jira/browse/WICKET-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980063#action_12980063
]
Richard Nichols commented on WICKET-3320:
-----------------------------------------
Sorry, I narrowed down the issue to Chrome's over-zealous caching. I was able
to reproduce the problem on two separate computers in a simple project where I
had upgraded from Wicket 1.4.0 to 1.4.15. But due to testing before and after,
Chrome had cached the buggy version of wicket-ajax.js from 1.4.0 and did not
detect that it changed with the update. Clearing the browser cache resolved the
issue.
Sorry about the bogus bug report.
> Ajax form submit does not invoke form, onsubmit in Javascript in Google Chrome
> ------------------------------------------------------------------------------
>
> Key: WICKET-3320
> URL: https://issues.apache.org/jira/browse/WICKET-3320
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.15
> Environment: Google Chrome 8.0.552.224 on Windows 7 x64
> Reporter: Richard Nichols
>
> Similar to previously fixed WICKET-3040 on Firefox, if you create a form with
> a onsubmit handler, or a bound event hander for submit, it is not invoked by
> an Ajax Submit Link/Button as expected on submit.
> e.g.
> <form wicket:id="myform" onsubmit="alert('hello world'); return true;">
> ...
> <a href="#" wicket:id="submit">submit</a>
> </form>
> and...
> class MyForm extends Form {
> MyForm() {
> super("myform");
> add(new AjaxSubmitLink("submit"));
> }
> }
> Would expect to see "hello world" prior to commit. Works in Firefox since
> 1.4.12 but not in Chrome.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
