[
https://issues.jboss.org/browse/RF-11065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Balunas updated RF-11065:
-----------------------------
Fix Version/s: 4.1.0.Final
Priority: Critical (was: Major)
> popupPanel: documentation omits forms requirement and contains wrong sample
> ---------------------------------------------------------------------------
>
> Key: RF-11065
> URL: https://issues.jboss.org/browse/RF-11065
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.0.0.Final
> Reporter: Ilya Shaikovsky
> Priority: Critical
> Fix For: 4.1.0.Final
>
>
> http://docs.jboss.org/richfaces/latest_4_0_X/Component_Reference/en-US/html/chap-Component_Reference-Panels.html#sect-Component_Reference-Panels-richpopupPanel
> 1) That note:
> "Placement
> The <rich:popupPanel> component is usually rendered in front of any other
> objects on the page. This is achieved by attaching the component to the
> <body> element of the page, and setting a very high "z-index" (t"
> actually have to be followed by one more critical note.
> "Limitation: defined by default popup *has to* have form element inside and
> not to be nested to external form in order submitting components/behaviors
> inside to work properly (because of repositioning in DOM). And to be able to
> be nested domElementAttachment should be changed to either form or parent."
> 2) Example 9.2. <rich:popupPanel> example
> confuses as form is around the panel! it should be either removed at all(as
> that sample not requires submission) or moved inside.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
