Using Wicket 1.4.3.
Since things are working right now without the wicket:link/ tag, I'm
going to leave it like that.
-Original Message-
From: bgooren [mailto:b...@iswd.nl]
Sent: Thursday, November 26, 2009 6:26 AM
To: users@wicket.apache.org
Subject: RE: onclick auto-added to script
Well, I don't use Spring integration in my projects, so I cannot tell you for
sure if that could be the reason for this. I do however find it unlikely
that Spring integration would alter html tags.
What you could try is step through the rendering process with a debugger and
see what's happening
I'm using wicket:link/ blocks around javascript references as well and have
never observed the behavior you describe. Do you auto-add a behavior to
components which adds the onclick value? It's being added from somewhere,
and is not default Wicket behavior. So it's either a browser plugin or an
as expected. That rules out a browser plugin being at
fault.
-Original Message-
From: bgooren [mailto:b...@iswd.nl]
Sent: Wednesday, November 25, 2009 7:07 AM
To: users@wicket.apache.org
Subject: Re: onclick auto-added to script tags?
I'm using wicket:link/ blocks around javascript
I have my HTML header links for CSS and JavaScript surrounded in a
wicket:link/ block so that it can resolve the context name, etc.
Problem is that it causes unexpected and peculiar behavior:
script type=text/javascript src=script/prototype.js/script
Becomes
script type=text/javascript