[
https://issues.apache.org/jira/browse/WICKET-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Rantalaiho updated WICKET-537:
-----------------------------------
Fix Version/s: (was: 1.4-M4)
1.5-M1
This is a new feature so belongs to 1.5, right?
With a superficial check, these ideas seem good to me. Should try it out in
code of course. Other opinions?
> AjaxForm needed for full featured handling
> ------------------------------------------
>
> Key: WICKET-537
> URL: https://issues.apache.org/jira/browse/WICKET-537
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 1.2.7
> Environment: Ubuntu Linux 2.6.20-15-generic
> Java 6
> Reporter: Julian Klappenbach
> Fix For: 1.5-M1
>
>
> Given that Ajax components are in popular use, a Form object to handle the
> specific issues caused by Ajax environments is necessary. The following
> features are recommended:
> Refactoring defaultSubmitButton to defaultSubmitComponent to enable
> AjaxSubmitLinks and AjaxSubmitButtons to be handled abstractly.
> Furthermore, The AjaxForm component should also feature an API method to
> accept the default component for focus. Establishing a default focus will
> enable the injection of javascript to set focus as appropriate when new
> panels become active.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
