[
https://issues.jboss.org/browse/RF-12592?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-12592:
------------------------------------
An alternative workaround is to not embed the _contextMenu_ directly in the table column,
but rather to create a top-level _contextMenu_ component and attach it to the extendedData
table, as in:
{code}
<rich:contextMenu target="table" mode="ajax">
<rich:menuItem label="View" render="popupContent"
oncomplete="#{rich:component('popup')}.show();" mode="ajax"
icon="/images/icons/open.gif"/>
</rich:contextMenu>
{code}
This is as demonstrated in the richfaces showcase. The bonus of this, is you create only
a single component element, instead of one component for each table row. This results in
a smaller component tree, and better performance. The downside is that you cannot tailor
the _contextMenu_ to the data in each row until macro-substitution (RF-11842) is supported
by the RF 4 _contextMenu_.
rich:contextMenu clipped by rich:extendedDataTable cells.
---------------------------------------------------------
Key: RF-12592
URL:
https://issues.jboss.org/browse/RF-12592
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.2.2.Final
Environment: browsers: Chrome, Firefox
application container: EAP 6
Reporter: Ilia Vassilev
Assignee: Brian Leathem
Fix For: 4.2.4
Attachments: brokenContextMenu.png, dataTable.png, dataTable.xhtml,
extendedDataTable.png
The context menu gets clipped by extendedDataTable cells. The same code works fine with
RF3 (see the attached screenshots and test page). The context menu is correctly displayed
if extendedDataTable is replaced with dataTable (attached dataTable.png).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira