Un rapide message pour prévenir qu’apparemment, Google Chrome, le nouveau navigateur de Google, basé sur le moteur WebKit (comme Safari) n’aime pas trop le javascript de Wicket.
En effet, j’ai pu constater que sur mon application NooWigen (dont j’ai fait une petite présentation dans ce post) ne se comporte pas normalement.
Si vous allez sur la page generate et que vous cliquez sur la case à cocher [Utiliser Ivy:], sur Firefox, un panel chargé dynamiquement via Ajax s’affiche, alors que sous Google Chrome, rien ne se passe.
Passons en mode [developement] et voyons ce que nous raconte le debuggueur de Wicket.
Firefox
INFO: focus removed from INFO: focus set on useIvy2 INFO: INFO: Initiating Ajax POST request on ;jsessionid=90A20FA2868CCE53007FC013D4DE9CDD?wicket:interface=:0:nooWiGenForm:useIvy::IBehaviorListener:0:&random=0.6504449022593362 INFO: Invoking pre-call handler(s)... INFO: Received ajax response (3965 characters) INFO: <?xml version="1.0" encoding="UTF-8"?><ajax-response><header-contribution encoding="wicket1" ><![CDATA[<head xmlns:wicket="http://wicket.apache.org"><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><component id="ivyPanel3" ><![CDATA[<div id="ivyPanel3"> ... blabla (du code html) ... </div> </div>]]></component></ajax-response> INFO: Response parsed. Now invoking steps... INFO: INFO: Initiating Ajax GET request on resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js INFO: Invoking pre-call handler(s)... INFO: Received ajax response (5977 characters) INFO: Invoking post-call handler(s)... INFO: INFO: Initiating Ajax GET request on resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js INFO: Invoking pre-call handler(s)... INFO: Received ajax response (61455 characters) INFO: Invoking post-call handler(s)... INFO: Using XMLHttpRequest transport INFO: INFO: Initiating Ajax GET request on resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug.js INFO: Invoking pre-call handler(s)... INFO: Received ajax response (8230 characters) INFO: Invoking post-call handler(s)... INFO: Response processed successfully. INFO: Invoking post-call handler(s)... INFO: last focus id was not set INFO: focus set on useIvy2 INFO: focus removed from useIvy2 INFO: focus set on useIvy2 INFO: focus removed from useIvy2 INFO: focus set on useIvy2 INFO: focus removed from useIvy2
Donc rien d’annormal.
Google Chrome
INFO: INFO: Initiating Ajax POST request on ?wicket:interface=:0:nooWiGenForm:useIvy::IBehaviorListener:0:&random=0.6218255823478103 INFO: Invoking pre-call handler(s)... INFO: Received ajax response (0 characters) INFO: ERROR: Error while parsing response: Could not find root <ajax-response> element INFO: Invoking post-call handler(s)... INFO: Invoking failure handler(s)...
Il faut que je regarde plus en détail ce qu’il se passe réellement entre le serveur et le navigateur pour savoir se qui se passe réellement.
ps : Sur la mailing list officielle de Wicket, il commence aussi a y avoir quelques bugs qui remontent (ex : le message de Cemal de jWeekEnd)
Imprimer cet article
