[ 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. -- 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

[ https://issues.jboss.org/browse/RF-11973?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11973: ------------------------------- Description: 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} was: 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> Forum Reference: https://community.jboss.org/message/645104#645104 (was: https://community.jboss.org/message/645104#645104) -- 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

[ https://issues.jboss.org/browse/RF-11973?page=com.atlassian.jira.plugin.s... ] Brendan Healey commented on RF-11973: ------------------------------------- Hi, I've been doing some additional testing (actually adding more contextMenus to the app!). What I've now noticed is that with a contextMenu attached to an extendedDataTable with target=, I reload the page and right click on a table row. The menu shows. If I then move the mouse away from the menu (still within the extendedDataTable, no mouse clicks) the menu hides, but subsequent right clicks just bring up the browser right click menu. I've not found any workaround other than page reload for this. -- 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

[ https://issues.jboss.org/browse/RF-11973?page=com.atlassian.jira.plugin.s... ] Pjotr Andreev commented on RF-11973: ------------------------------------ Hi, see the "Forum Reference" for workaround- just put one (first??) invisible menuItem into contextMenu and re-render all other visible menuItems, but not contextMenu. But the problem exists. -- 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

[ https://issues.jboss.org/browse/RF-11973?page=com.atlassian.jira.plugin.s... ] Pjotr Andreev commented on RF-11973: ------------------------------------ Hi, You welcome! The workaround is (the context menu`s items #cmi1 and #cmi2 will be re-rendered on row selection change, then, after #cmi2 action, the table and contextMenu will be re-rendered): <rich:extendedDataTable id="table" selection=#{listener.selection}> <a4j:ajax execute="@form" event="selectionchange" listener="#{listener.selectionChanged}" render=":cmi1 :cmi2" limitRender="true"/> <rich:column>Column Content</rich:column> </rich:extendedDataTable> <rich:contextMenu id="contextMenu" mode="ajax" target="table" showEvent="click"> <rich:menuItem id="cmi0" label="I am invisible" mode="client" style="display: none;"/> <rich:menuItem id="cmi1" label="I am visible" mode="client"/> <rich:menuItem id="cmi2" label="I am visible too" mode="ajax" render="table contextMenu" limitRender="true"/> </rich:contextMenu> The sequence of execution is: 1. click event sent to the table 2. contextMenu is shown, since it reacts on click event 3. the onchange event is processed and AJAX request sent to the server 4. the partial update response with new #cmi1 and #cmi2 item contents is processed on the client and 5. the DOM of #cmi1 and #cmi2 is replaced in the contextMenu popup already shown And by the way every time the table is rendered, the contextMenu MUST be re-rendered as well, otherwise the "showEvent" becomes unregistered... -- 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

[ https://issues.jboss.org/browse/RF-11973?page=com.atlassian.jira.plugin.s... ] Philip Maes commented on RF-11973: ---------------------------------- When you do this workaround, as Brendan says, it appears only one time and when the contextMenu hides there is a javascript error: http://img836.imageshack.us/img836/4586/contextmenu1.png -- 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

[ https://issues.jboss.org/browse/RF-11973?page=com.atlassian.jira.plugin.s... ] Nikolai Alexeev commented on RF-11973: -------------------------------------- Pjotr's workaround doesn't work for dynamically generated context menu when menuItems are generated in <c:forEach/> cycle because you can't wrap it in some block to rerender it: contextMenu just ignores such block and doesn't render anything. -- 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

[ https://issues.jboss.org/browse/RF-11973?page=com.atlassian.jira.plugin.s... ] Gavin Lussi edited comment on RF-11973 at 9/26/12 6:03 AM: ----------------------------------------------------------- I, too, get the exact same problem as Brendan/Philip when including the id of the context menu in a render list. The current "work around" isn't a work around, so I currently have no way to construct a menu with dynamically loaded options depending on which row in a table is right clicked. (Also, we aren't using any c:foreach, so that isn't the problem in my case) was (Author: gmlussi): I, too, get the exact same problem as Brendan/Philip when including the id of the context menu in a render list. The current "work around" isn't a work around, so I currently have no way to construct a menu with dynamically loaded options depending on which row in a table is right clicked. -- 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