[
https://issues.jboss.org/browse/RF-11973?page=com.atlassian.jira.plugin.s...
]
Gavin Lussi commented on RF-11973:
----------------------------------
My previous comment makes me think the workaround didn't work for me, anyway, and I do
remember being faced with the JavaScript error...
However, even if it had worked (or works in some situations), it doesn't work in the
case of built-in filtering and sorting, because AFAIK there is no way to add an ajax
re-render of the context menu when using the built in (RF 4.3.0+) filter/sort controls.
Much like I described in the above thread.
So, if the two issues are grouped, the suggested workaround definitely only applies to
some situations, and won't always be a workable solution.
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