Unfortunately that patch doesn't solve the problem. I've added a
comment to the issue with a different patch which addresses our problem
and the problem mentioned in the issue (I hope :) ).
Thanks,
Meetesh
Thijs wrote:
See
https://issues.apache.org/jira/browse/WICKET-1426
Meetesh Karia schreef:
Hi all,
We recently upgraded to Wicket 1.3.2 from Wicket 1.3.1 and we're
seeing a bug with ajax behavior in Firefox (2.0.0.13 on Windows
Vista). Basically, the following header is returned from an ajax call:
<?xml version="1.0"
encoding="UTF-8"?><ajax-response><header-contribution
encoding="wicket1" ><![CDATA[<head
xmlns:wicket="http://wicket.apache.org";>
<script src="/templates/mediaplayer/swfobject.js"
language="javascript"></script> <script type="text/javascript"
src="../../resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js"></script>
<script type="text/javascript"
src="../../resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js"></script>
<script type="text/javascript"
src="../../resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug.js"></script>
<script type="text/javascript"
id="wicket-ajax-debug-enable"><!--/*--><![CDATA[/*><!--*/
wicketAjaxDebugEnable=true;
/*-->]^]^>*/</script>
</head>]]></header-contribution>
The page this is called from has a URL that looks like this
http://host/2008/foo/bar
In Wicket 1.3.1, the script /templates/mediaplayer/swfobject.js gets
correctly loaded from
http://host/templates/mediaplayer/swfobject.js
However, in Wicket 1.3.2, it is incorrectly loaded from
http://host/2008/foo//templates/mediaplayer/swfobject.js
This appears to be related to one of these two changes:
http://fisheye6.cenqua.com/browse/wicket/trunk/jdk-1.4/wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js?r1=614229&r2=619539
http://fisheye6.cenqua.com/browse/wicket/trunk/jdk-1.4/wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js?r1=627225&r2=628015
I haven't narrowed it down but replacing wicket-ajax.js with the
version from 1.3.1 makes it work again.
Should I file a bug for this? Or is this going to be the new
behavior going forward for Firefox? Also, I'm guessing that the
safest way to work around this problem is to remove those two changes
and temporarily use a local build of wicket, right?
Thanks,
Meetesh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
