[richfaces-issues] [JBoss JIRA] (RF-12080) rich:hotKey usage clears body onload attribute

Michael Heinen (JIRA) jira-events at lists.jboss.org
Fri Apr 6 08:23:48 EDT 2012


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

Michael Heinen updated RF-12080:
--------------------------------

    Attachment: sampleWebApps.zip


Attaches are two war files:
1) onload42.war is for JSF 2.1: Richfaces 4.2 and myFaces 2.1.6
2) onloal333.war is for JSF 1.2: Richfaces 3.3.3 and MyFaces 1.2.10

Both wars are without libs to minimize size. Tomahawk is not required at all for reproduction.

Both web archives contain two xhtml files:
1) hotkey.xhtml contains rich:hotkey
2) noHotkey.xhtml does not contain rich.hotkey

With richfaces 3.3.3 the body onload is processed for both xhtml files.

With richfaces 4.2  the body onload is processed only if rich:hotkey is not used.

Note that in all xhtml files a js script is in the head which writes into the document. Without this script it's always working!

                
> 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
>         Attachments: sampleWebApps.zip
>
>
> 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

       



More information about the richfaces-issues mailing list