[richfaces-issues] [JBoss JIRA] Reopened: (RF-8624) hotkey destroyed not completely

[Jan Vermeulen (JIRA)]

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

Jan Vermeulen reopened RF-8624:
-------------------------------



Could you please try to reproduce again with this code: 

<h:form>
	<input type="text" id="textInput" /> 
	<a4j:outputPanel ajaxRendered="true"> 
		<rich:hotKey key="K" handler="alert('hotkey')" selector="#textInput"/> 
		#{forum5Bean.currentTime} 
	</a4j:outputPanel> 
	<a4j:commandLink value="Update hotkey" /> 
</h:form>

Now, for every time you click on the link, the hotkey is executed an extra time. 
e.g. If you click the link twice and press the hotkey afterwards, the alert('hotkey') is shown 3 times.

Thanks

> hotkey destroyed not completely
> -------------------------------
>
>                 Key: RF-8624
>                 URL: https://jira.jboss.org/jira/browse/RF-8624
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-output, performance
>         Environment: richfaces 3.3.1GA, 
>            Reporter: Jan Vermeulen
>            Assignee: Nick Belaevski
>
> On my form, i have a search pop up that can be triggered in two ways: by a button and by a hotkey.
> Whenever a search is performed, the page section where the button and hotkey are defined is rerendered. 
> If i use the hotkey again afterwards, the handler of the hotkey is called twice. 
> If i put the definition of the hotkey in a page section that is not redendered. The problem does not occur. 
> I believe this issue is related to the following ticket: https://jira.jboss.org/jira/browse/RF-8074. Where a similar problem occurs with a context menu. The problem there is that the context menu item isn't destroyed correctly: e.g. the listeners are not destroyed.
> I have taken a look at the javascript 'destroy' method for the hotkey and have seen that it is also not destroying the listeners. Therefore i think that the same/similar fix as for ticket RF-8074 should be applied.
> Thanks for looking at this issue
> Regards,
> Jan

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira