[
https://issues.jboss.org/browse/RF-11973?page=com.atlassian.jira.plugin.s...
]
Brendan Healey commented on RF-11973:
-------------------------------------
Just realised that there's a fairly obvious workaround, use contextMenu
id="ctx1"
and include the id in the render list render="mytable ctx1". It would be a bit
irritating to have to remember to do this for all eternity, but it resolves the
immediate problem.
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)
Affects Versions: 4.2.0.CR1
Environment: chrome browser / glassfish 3.1.1 / mojarra 2.1.6
Reporter: Brendan Healey
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.
<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>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira