[
https://issues.apache.org/jira/browse/TOMAHAWK-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587779#action_12587779
]
Ernst Fastl commented on TOMAHAWK-1226:
---------------------------------------
In order to resolve this issue, I suggest that we introduce a PPRWindowCtrl
which stores the triggers, patterns and so on.
PPRCtrl are at the moment connected to the form. That should only be used for
eventHandler connections. The rest should be
window bound IMO.
> PPRPanelGroup support for multiple forms in a page is broken
> ------------------------------------------------------------
>
> Key: TOMAHAWK-1226
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1226
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: PPRPanelGroup
> Affects Versions: 1.1.7-SNAPSHOT
> Reporter: Catalin Kormos
> Assignee: Ernst Fastl
> Fix For: 1.1.7-SNAPSHOT
>
>
> When a triggering element is part of another form than a triggered element,
> PPRPanelGroup doesn't behave well. The cause is related to where the
> triggered element is kept, and a possible solution is to keep it in the
> "window" object.
> Please look in ppr.js at
> "org.apache.myfaces.PPRCtrl.prototype.elementOnEventHandler" and at
> "org.apache.myfaces.PPRCtrl.prototype.formSubmitReplacement"; replacing
> this.triggeredElement with window.triggeredElement fixes the problem, but it
> might not be the best solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
