Thanks,
https://issues.apache.org/jira/browse/WICKET-2457
-Heikki
-Original Message-
From: Matej Knopp [mailto:matej.kn...@gmail.com]
Sent: 9. syyskuuta 2009 0:10
To: users@wicket.apache.org
Subject: Re: Flash/ExternalInterface does not work in IE if movie is fetched
via Wicket/Ajax
There is a bug in wicket-ajax.js:268 (1.4.1) that breaks
IE+Flash/ExternalInterface:
// place all newly created elements before the old element
while(tempParent.childNodes.length 0) {
var tempElement = tempParent.childNodes[0];
Well, it's not exactly wrong. Looks like an IE quirk to me. But I
suppose we can just move the element anyway.
-Matej
On Tue, Sep 8, 2009 at 11:10 PM, Matej Knoppmatej.kn...@gmail.com wrote:
Hi,
can you create jira issue with problem description? The code indeed
looks wrong I can fix it once
Hi,
can you create jira issue with problem description? The code indeed
looks wrong I can fix it once the issue is created.
-Matej
On Tue, Sep 8, 2009 at 9:59 PM, Heikki
Uotinenheikki.uoti...@syncrontech.com wrote:
There is a bug in wicket-ajax.js:268 (1.4.1) that breaks
There is a problem with IE/ExternalInterface if movie is added to DOM f.ex
appendChild
JavaScript functions are called but they do not return any value.
This is clearly MS problem but could IE specific function in wicket-ajax.js be
adjusted somehow ?
Simple test case has
var
