It is a major fix, (and there are also other important fixes), but it seems that there are still some issues with it, although I'm not able currently to reproduce them. So I'm waiting for more info, maybe it's only something like need for clean build or javascript cache...
Anyway, have you tried current 1-x with safari? Just to make sure I haven't broken anything :) Martijn Dashorst wrote: > How are we doing for Wicket 1.2.3? I recently learned (from the > userlist) that the header contribution problem for ajax updates now > works :-), so that is a major fix and it deserves to be used. > > Any ideas on progress or stability of our current 1.x branch? > > Martijn > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
