You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@click.apache.org by "Bob Schellink (JIRA)" <ji...@apache.org> on 2009/03/28 16:54:50 UTC

[jira] Commented: (CLK-508) Move isFormSubmission check to Field

    [ https://issues.apache.org/jira/browse/CLK-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693459#action_12693459 ] 

Bob Schellink commented on CLK-508:
-----------------------------------

Changes committed.

One problem with this change is that custom Fields that override onProcess will need to add this check otherwise there is the potential issue where two Submit buttons in different forms would both be processed. If they have the same name both their Listeners would be fired.

> 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.