[richfaces-issues] [JBoss JIRA] Updated: (RF-8541) Null Parent Node

[Alexander Smirnov (JIRA)]

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

Alexander Smirnov updated RF-8541:
----------------------------------

     Original Estimate: 0 minutes
    Remaining Estimate: 0 minutes


The script has been designed to work on standalone page. In the portal, portlets can be updated by AJAX. In this case scripts are loaded in XMLHttpRequest context there document.write does not attached to the page, so <script> element created by that function has no parents.
I replaced it by DOM function and added check for parent node before element cleanup.

> Null Parent Node
> ----------------
>
>                 Key: RF-8541
>                 URL: https://jira.jboss.org/jira/browse/RF-8541
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: browser compatibility, portal
>    Affects Versions: 3.3.3.CR1
>            Reporter: Fernando Ribeiro
>            Assignee: Alexander Smirnov
>             Fix For: 3.3.3.Final
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> While using portlets with JBoss Portlet Bridge 2.0.0.CR1 in JBoss Portal 2.7.2, I get an "script.parentNode is null or not an object" in IE8 (but not in Firefox 3.6) from ui.pack.js:
> function checkReadyState() {
>   if (script.readyState=="complete") {
>     script.parentNode.removeChild(script);
>     callDomLoadFunctions()
>   }
> }
> The script is added to the page as follows, inside a DIV, for each portlet in the page:
> <script src="/portal/auth/portal/default/sample/SamplePortletWindow?rfRes=%2Forg%2Frichfaces%2Fui.pack.js&amp;action=b&amp;cacheability=PAGE" type="text/javascript"></script>
> Other users of the JBoss Portlet Bridge may want to know that I am using the WRAP_SCRIPTS context param.
> I wasn't able to find the cause of the issue, but found a way to work around it:
> function checkReadyState() {
>   if (script.parentNode && script.readyState=="complete") {
>     script.parentNode.removeChild(script);
>     callDomLoadFunctions()
>   }
> }
> Can you please investigate the issue and/or consider adding the workaround to the next 3.x release?

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