[richfaces-svn-commits] JBoss Rich Faces SVN: r22900 - modules/docs/trunk/Component_Reference/src/main/docbook/en-US.
Author: bleathem
Date: 2011-11-07 16:38:49 -0500 (Mon, 07 Nov 2011)
New Revision: 22900
Modified:
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Panels.xml
Log:
RFPL-1495: Updated the popupPanel documentation, with details of embedding a form, or
attaching to an exsiting form's DOM element
Modified:
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Panels.xml
===================================================================
---
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Panels.xml 2011-11-07
21:05:27 UTC (rev 22899)
+++
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Panels.xml 2011-11-07
21:38:49 UTC (rev 22900)
@@ -243,7 +243,7 @@
<term><function>lastItem()</function></term>
<listitem>
<para>
- Switch to and display the first item, the previous item, the next item,
or the last item.
+ Get the name of the first item, the previous item, the next item, or the
last item.
</para>
</listitem>
</varlistentry>
@@ -587,7 +587,7 @@
The <sgmltag><rich:popupPanel></sgmltag> component is
usually rendered in front of any other objects on the page. This is achieved by attaching
the component to the <sgmltag><body></sgmltag> element of the
page, and setting a very high <emphasis>"z-index"</emphasis> (the
stack order of the object). This approach is taken because relatively-positioned elements
could still overlap the pop-up panel if they exist at higher levels of the
<acronym>DOM</acronym> hierarchy, even if their z-index is less than the
<sgmltag><rich:popupPanel></sgmltag> component.
</para>
<para>
- To avoid form limitation of the pop-up panel on pages where no such elements exist,
the <sgmltag><rich:popupPanel></sgmltag> component can be
reattached to its original <acronym>DOM</acronym> element by setting
<varname>domElementAttachment</varname> to either
<literal>parent</literal> or <literal>form</literal>.
+ If the <sgmltag><rich:popupPanel></sgmltag>
is to participate in submitting child components/behaviors, then a form element must be
nested within the <sgmltag><rich:popupPanel></sgmltag>.
Alternatively, if no overlapping elements exist, the
<sgmltag><rich:popupPanel></sgmltag> component can be reattached
to its original <acronym>DOM</acronym> element by setting
<varname>domElementAttachment</varname> to either
<literal>parent</literal> or <literal>form</literal>.
</para>
</important>
</section>
@@ -969,7 +969,7 @@
<term><function>lastItem()</function></term>
<listitem>
<para>
- Switch to and display the first item, the previous item, the next item,
or the last item.
+ Get the name of the first item, the previous item, the next item, or the
last item.
</para>
</listitem>
</varlistentry>
@@ -1231,7 +1231,7 @@
<term><function>lastItem()</function></term>
<listitem>
<para>
- Switch to and display the first item, the previous item, the next item,
or the last item.
+ Get the name of the first item, the previous item, the next item, or the
last item.
</para>
</listitem>
</varlistentry>