[ 
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682063#comment-12682063
 ] 

Lukáš Fryč commented on RF-12080:
---------------------------------

Michael, could you please try to debug what's going on?

There are my thoughts on the issue:

[hotKey.js:26|https://github.com/richfaces/components/blob/develop/misc/ui/src/main/resources/META-INF/resources/org.richfaces/hotkey.js#L26]
 specifies following handler:

{code:javascript}
$(document).ready($.proxy(function() {
    this.__bindDefinedHandlers();
}, this));
{code}

which is pretty the same you have tried.

You can set the breakpoint in the 
[jquery.hotkeys.js|https://github.com/richfaces/components/blob/develop/misc/ui/src/main/resources/META-INF/resources/org.richfaces/jquery.hotkeys.js#L41]
 and refresh the page. If the breakpoint will be hit, then this issue might be 
related to {{rich:hotkey}} component.


If you are not capable to debug JavaScript, then please provide me sample of 
the usage which I could simply grab and deploy. Please minimize such sample to 
be without any external dependencies except Tomahawk.
                
> rich:hotKey usage clears body onload attribute
> ----------------------------------------------
>
>                 Key: RF-12080
>                 URL: https://issues.jboss.org/browse/RF-12080
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.2.0.Final
>         Environment: myfaces 2.1.6, tomahawk 1.1.11
>            Reporter: Michael Heinen
>            Assignee: Lukáš Fryč
>            Priority: Minor
>              Labels: myfaces, tomahawk, waiting_on_user
>
> I'm happy to see rich:hotKey in richfaces 4.2, I used it already with 
> richfaces 3.3.3.
> One thing I noticed now is that the onload attribute of t:documentboy is 
> cleared on clientside as soon as rich:hotKey is used on a page. Maybe caused 
> by jquery usage?
> From my pov this should be either fixed or documented in the component guide 
> as well as in the showcase sample.
> Workaround is obvious: Instead of onload use document.ready

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

       

_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues

Reply via email to