You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2009/09/10 00:20:01 UTC

[jira] Assigned: (WICKET-2457) Flash/ExternalInterface does not work in IE if movie is fetched via Wicket/Ajax

     [ https://issues.apache.org/jira/browse/WICKET-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg reassigned WICKET-2457:
-------------------------------------

    Assignee: Matej Knopp

> Flash/ExternalInterface does not work in IE if movie is fetched via Wicket/Ajax
> -------------------------------------------------------------------------------
>
>                 Key: WICKET-2457
>                 URL: https://issues.apache.org/jira/browse/WICKET-2457
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.1
>         Environment: IE6/7 FlashCS4/AS3
>            Reporter: Heikki Uotinen
>            Assignee: Matej Knopp
>            Priority: Critical
>         Attachments: noname.zip
>
>
> If Flash movie CS4/AS3 is added with Wicket/Ajax then AS3/ExternalInterface.call
> does not return any value event it calls JavaScript functions, also ExternalInterface.objectID is null.
> Suggestion is that wicket-ajax.js:268 (1.4.1) breaks IE+Flash/ExternalInterface:
>         // place all newly created elements before the old element
>         while(tempParent.childNodes.length > 0) {
>                 var tempElement = tempParent.childNodes[0];
> >>>>>>           tempParent.removeChild(tempElement); <<<<<
>                 parent.insertBefore(tempElement, element);
>                 tempElement = null;
>         }
> This "removeChild" breaks Flash/ExternalInterface in IE. If "removeChild" is removed then everything works fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.