> Unfortunately, this was just one little nice-to-have enhancement I > thought I'd throw in while I was making changes. It works fine until I > put the code into it's production environment, which means it's being > called as part of a Plumtree portal. And there something falls apart > when I do this. It's not Wicket's fault, of course, but some strange > interaction with Plumtree's Javascript. In Firefox the fragment > identifier is gone; in IE I get an "Internal Error." Although the fault > is clearly with Plumtree that doesn't help me. I think "nice-to-have" > is going to turn into "yes-it-would-have-been-nice". :-)
Could you tell us more about what doesn't work/ what kind of problems you are experiencing en what your environment looks like? I'd say there not much that can go wrong with anchors? Eelco _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
