Any ideas on how this might be fixed (accept for telling people not to use a retarded browsers like IE)? Can we open an issue for it to track it?
Eelco On 2/18/07, Frank Bille <[EMAIL PROTECTED]> wrote: > Oh yeah that was 1.3. So sorry no luck. It has nothing to do with how wicket > handles urls, but how IE interprets url() for behavior. ------------------------------------------------------------------------- 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-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
