[
https://issues.apache.org/jira/browse/CLK-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693531#action_12693531
]
Malcolm Edgar commented on CLK-508:
-----------------------------------
Sticking non field controls inside a form is generally a bad idea, as it break
the basic HTML GET/POST model. If you put a table in a field and the users
edits some form fields, then clicks on an non field element such as an action
link, the form state will not be preserved in the GET request and the user
experience is confusing.
I am pretty uncomfortable about this event model change, and am concerned that
it could break a lot of existing code.
> Move isFormSubmission check to Field
> ------------------------------------
>
> Key: CLK-508
> URL: https://issues.apache.org/jira/browse/CLK-508
> Project: Click
> Issue Type: Improvement
> Components: core, extras
> Reporter: Bob Schellink
> Assignee: Bob Schellink
> Fix For: 2.1.0
>
>
> Currently Form determines whether its child controls should be processed
> based on whether Form was submitted or not. This restriction works well for
> Fields, however problems arise when adding components such as ActionLink,
> Tables and Trees which need to be processed even when Form is not submitted.
> Ajax based Fields also has this problem and often need to be added to the
> Page in order to be processed.
> This issue will try and address the problem by introducing a new Field method
> called "canProcess". This method will return true if the Form is submitted or
> if its a Ajax request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
