8:39 a.m.
Michael Heinen created RF-12080:
-----------------------------------
Summary: 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
Priority: Minor
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
6:11 p.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-12080:
-------------------------------
Fix Version/s: 4.2.1.CR1
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
Priority: Minor
Fix For: 4.2.1.CR1
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
4:10 p.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč reassigned RF-12080:
-------------------------------
Assignee: Lukáš Fryč
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
Fix For: 4.2.1.CR1
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
10:20 a.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12080:
---------------------------------
Could you please try if {{t:documentBody}} works when you place following script inside
the body?
{code:Javascript}
$(document).ready(function() {
document.title = 'xyz';
});
{code}
Could you please send the respected source code generated by {{<t:documentBody
onload="...">}}?
----
Anyway I think the proper fix is on the Tomahawk's side, since it seems it is doing
something wrong, because simply using {{<body onload="...">}} don't
break by using {{document.ready}}:
{code:html}
<html>
<head>
<script type="text/javascript"
src="jquery-1.7.1.js"></script>
</head>
<body onload="alert('2')">
<script type="text/javascript">
jQuery(document).ready(function($) {
alert('1');
});
</script>
</body>
</html>
{code}
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
Fix For: 4.2.1.CR1
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
10:20 a.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-12080:
----------------------------
Workaround Description: Use
[{{$(document).ready(handler)}}|http://api.jquery.com/ready/] instead of
{{<t:documentBody onload="handler">}}.
Workaround: Workaround Exists
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
Fix For: 4.2.1.CR1
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
10:22 a.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-12080 at 3/27/12 4:21 AM:
----------------------------------------------------------
Could you please try if {{t:documentBody}} works when you place following script inside
the body?
{code:Javascript}
$(document).ready(function() {
document.title = 'xyz';
});
{code}
Could you please send the respected source code generated by {{<t:documentBody
onload="...">}}?
----
Anyway I think the proper fix is on the Tomahawk's side, since it seems it is doing
something wrong, because simple {{<body onload="...">}} don't break by
using {{document.ready}}:
{code:html}
<html>
<head>
<script type="text/javascript"
src="jquery-1.7.1.js"></script>
</head>
<body onload="alert('2')">
<script type="text/javascript">
jQuery(document).ready(function($) {
alert('1');
});
</script>
</body>
</html>
{code}
was (Author: lfryc):
Could you please try if {{t:documentBody}} works when you place following script
inside the body?
{code:Javascript}
$(document).ready(function() {
document.title = 'xyz';
});
{code}
Could you please send the respected source code generated by {{<t:documentBody
onload="...">}}?
----
Anyway I think the proper fix is on the Tomahawk's side, since it seems it is doing
something wrong, because simply using {{<body onload="...">}} don't
break by using {{document.ready}}:
{code:html}
<html>
<head>
<script type="text/javascript"
src="jquery-1.7.1.js"></script>
</head>
<body onload="alert('2')">
<script type="text/javascript">
jQuery(document).ready(function($) {
alert('1');
});
</script>
</body>
</html>
{code}
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
10:22 a.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-12080:
----------------------------
Fix Version/s: (was: 4.2.1.CR1)
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
10:22 a.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-12080 at 3/27/12 4:22 AM:
----------------------------------------------------------
Could you please try if {{t:documentBody}} works when you place following script inside
the body?
{code:Javascript}
$(document).ready(function() {
document.title = 'xyz';
});
{code}
Could you please send the respected source code generated by {{<t:documentBody
onload="...">}}?
----
Anyway I think the proper fix is on the Tomahawk's side, since it seems it is doing
something wrong, because simple {{<body onload="...">}} don't break by
using {{document.ready}}:
{code:html}
<html>
<head>
<script type="text/javascript"
src="jquery-1.7.1.js"></script>
</head>
<body onload="alert('2')">
<script type="text/javascript">
jQuery(document).ready(function($) {
alert('1');
});
</script>
</body>
</html>
{code}
Both alerts are shown.
was (Author: lfryc):
Could you please try if {{t:documentBody}} works when you place following script
inside the body?
{code:Javascript}
$(document).ready(function() {
document.title = 'xyz';
});
{code}
Could you please send the respected source code generated by {{<t:documentBody
onload="...">}}?
----
Anyway I think the proper fix is on the Tomahawk's side, since it seems it is doing
something wrong, because simple {{<body onload="...">}} don't break by
using {{document.ready}}:
{code:html}
<html>
<head>
<script type="text/javascript"
src="jquery-1.7.1.js"></script>
</head>
<body onload="alert('2')">
<script type="text/javascript">
jQuery(document).ready(function($) {
alert('1');
});
</script>
</body>
</html>
{code}
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
3:59 p.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Michael Heinen commented on RF-12080:
-------------------------------------
I tested the manually added scripts:
a) document.title = 'xyz';
b) jQuery(document).ready(function($) {alert('1');});
Both work in combination with tomahawk onload attribute
However the richfaces hotkey does not work with it and also not with standard body tag.
Sample usage:
<rich:hotKey key="backspace" handler="return false;"
disableInInput="true"/>
So it's independent of tomahawk.
From my pov this should be at least documented in the tag description
or user guide.
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
3:39 p.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
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...]
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/mi...]
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
3:41 p.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-12080 at 4/5/12 9:40 AM:
---------------------------------------------------------
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...]
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:41|https://github.com/richfaces/components/blob/develop...]
and refresh the page. If the breakpoint will be hit, then this issue might be related to
{{rich:hotkey}} component.
You can use Firebug for Firefox or Chrome Web Inspector for debugging JavaScript.
Be sure to use uncompressed RichFaces resources.
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.
was (Author: lfryc):
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...]
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/mi...]
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
3:41 p.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-12080 at 4/5/12 9:40 AM:
---------------------------------------------------------
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...]
specifies following handler:
{code:javascript}
$(document).ready($.proxy(function() {
this.__bindDefinedHandlers();
}, this));
{code}
which is pretty the same you have tried, therefore I don't expect there any issue.
You can set the breakpoint in the
[jquery.hotkeys.js:41|https://github.com/richfaces/components/blob/develop...]
and refresh the page. If the breakpoint will be hit, then this issue might be related to
{{rich:hotkey}} component.
You can use Firebug for Firefox or Chrome Web Inspector for debugging JavaScript.
Be sure to use uncompressed RichFaces resources.
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.
was (Author: lfryc):
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...]
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:41|https://github.com/richfaces/components/blob/develop...]
and refresh the page. If the breakpoint will be hit, then this issue might be related to
{{rich:hotkey}} component.
You can use Firebug for Firefox or Chrome Web Inspector for debugging JavaScript.
Be sure to use uncompressed RichFaces resources.
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
2:23 p.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
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
2:25 p.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Michael Heinen edited comment on RF-12080 at 4/6/12 8:25 AM:
-------------------------------------------------------------
Attached are two war files:
1) onload42.war is for JSF 2.1: Richfaces 4.2 and myFaces 2.1.6
2) onload333.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!
was (Author: mhn):
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
4:38 p.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12080:
---------------------------------
Thanks Michael, I will grab your samples next week and dive into them.
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
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
4:56 p.m.
[
https://issues.jboss.org/browse/RF-12080?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-12080:
----------------------------
Fix Version/s: 4.3-Tracking
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
Fix For: 4.3-Tracking
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
4652
days inactive
4670
days old
richfaces-issues@lists.jboss.org
15 comments
3 participants
participants (3)
-
Brian Leathem (JIRA) -
Lukáš Fryč (JIRA)
-
Michael Heinen (JIRA)