[
https://issues.jboss.org/browse/RF-11973?page=com.atlassian.jira.plugin.s...
]
Juraj Húska commented on RF-11973:
----------------------------------
Hey Brian,
I reproduced the issue on showcase, on
[
this|https://github.com/jhuska/showcase/tree/803276] branch.
The issue is that the {{contextMenu}} is broken after the filtering/sorting on a
{{extendedDataTable}}, which is IMHO the same as this one.
That behavior was described in this community thread:
https://community.jboss.org/message/803276#803276
Do you think that those two descriptions are related ? Or should I create a new issue for
that sorting/filtering.
rich:contextMenu - after ajax re-render of table contextMenu no
longer works
----------------------------------------------------------------------------
Key: RF-11973
URL:
https://issues.jboss.org/browse/RF-11973
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-menu
Affects Versions: 4.2.0.CR1, 4.3.2
Environment: chrome browser / glassfish 3.1.1 / mojarra 2.1.6
Reporter: Brendan Healey
Fix For: 5-Tracking
With the following code structure, when the page is first rendered
you can right click on a row in the table and the context menu appears.
After pushing the commandButton subsequent right clicks show the
default browser right click menu, and not the context menu.
{code}
<rich:extendedDataTable id="mytable">
...
</rich:extendedDataTable>
<a4j:commandButton value="push" render="mytable"/>
<rich:contextMenu target="mytable" mode="ajax">
<rich:menuItem label="Delete"
mode="ajax"
onclick="alert('hello, world!')"/>
</rich:contextMenu>
{code}
--
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