[jira] Updated: (TRINIDAD-842) client-side validation and ppr

["Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>]

     [ https://issues.apache.org/jira/browse/TRINIDAD-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerhard Petracek updated TRINIDAD-842:
--------------------------------------

    Status: Patch Available  (was: Open)

> client-side validation and ppr
> ------------------------------
>
>                 Key: TRINIDAD-842
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-842
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.0.3-core, 1.0.4-core
>         Environment: i found this issue at the trinidad version 1.0.3 and 1.0.4 - in my opinion also other versions are affected
>            Reporter: Gerhard Petracek
>
> scenario: to show/hide input components via ppr (which are e.g. in a logical area - which is represented by a parent component -> if the area is hidden, it isn't in the dom.)
> (the rendered attribute is used here -> the parent component (of the previous mentioned parent component) has to be refreshed to show this area via ppr again)
> however, if this area is rendered and the input components of this area use client-side validation - javascript source-code gets added (dynamically) to the form.
> after hiding the area again this client-side validation source-code remains in place (until the whole form gets refreshed).
> -> if a user tries to get to the next view, the client-side validation source-code tries to validate components which aren't in the dom any more.
> workaround:
> don't use ppr for this area - trigger ppr for the complete form (i know - it's not nice to do that - it's just a workaround)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.