[richfaces-issues] [JBoss JIRA] (RF-12592) rich:contextMenu clipped by rich:extendedDataTable cells.

Brian Leathem (JIRA) jira-events at lists.jboss.org
Tue Nov 13 22:17:18 EST 2012


     [ https://issues.jboss.org/browse/RF-12592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-12592:
-------------------------------

    Workaround Description: 
h4.Workaround 1:

A work around is to set the following css rule:

{code}
.rf-edt-c {
    overflow: visible;
}
{code}

To use this workaround, make sure this css rule is included after the extendedDataTable css file.  The recommended way to do this is to define this css using an _h:outputStyleSheet_ placed as the very last element in your page.

*Advantage*: you can tailor the _contextMenu_ to each table row value.

*Dis-advantage*: you create many _componentMenu_ components, creating a larger component tree, and poorer performance.
----
h4.Workaround 2:

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|http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=contextMenu&sample=table&skin=blueSky].  

*Advantage*: you create only a single component element, instead of one component for each table row yielding a smaller component tree, and better performance.  

*Dis-advantage*: you cannot tailor the _contextMenu_ to the data in each row until macro-substitution (RF-11842) is supported by the RF 4 _contextMenu_.

  was:
A work around is to set the following css rule:

{code}
.rf-edt-c {
    overflow: visible;
}
{code}

To use this workaround, make sure this css rule is included after the extendedDataTable css file.  The recommended way to do this is to define this css using an _h:outputStyleSheet_ placed as the very last element in your page.


    
> 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


More information about the richfaces-issues mailing list