[richfaces-planning-issues] [JBoss JIRA] Moved: (RFPL-1495) popupPanel: documentation omits forms requirement and contains wrong sample
[
https://issues.jboss.org/browse/RFPL-1495?page=com.atlassian.jira.plugin....
]
Jay Balunas moved RF-11065 to RFPL-1495:
----------------------------------------
Project: RichFaces Planning (was: RichFaces)
Key: RFPL-1495 (was: RF-11065)
Workflow: jira (was: GIT Pull Request workflow )
Affects Version/s: 4.0.0.Final
(was: 4.0.0.Final)
Component/s: doc
(was: doc)
Fix Version/s: 4.1.0.Final
(was: 4.1.0.Final)
popupPanel: documentation omits forms requirement and contains wrong
sample
---------------------------------------------------------------------------
Key: RFPL-1495
URL: https://issues.jboss.org/browse/RFPL-1495
Project: RichFaces Planning
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/ht...
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