:
http://apache-wicket.1842946.n4.nabble.com/Disabled-Auto-link-bookmarkable-page-tp1888129p4649502.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
-wicket.1842946.n4.nabble.com/Disabled-Auto-link-bookmarkable-page-tp1888129p4649503.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional
I guess the view is that using a span gives safe markup in any situation.
The disableLink() method can be overriden it if you need cleaner markup
in a particular situation.
Cassio wrote:
But it would change only the em and /em default markups and not the
span that replace the a tag at
Ok, Thanks!
2009/7/27 Iain Reddick iain.redd...@beatsystems.com
I guess the view is that using a span gives safe markup in any situation.
The disableLink() method can be overriden it if you need cleaner markup in
a particular situation.
Cassio wrote:
But it would change only the em and
Hello everybody!
Does anyone know for what reason an disabled auto link gets nested inside a
span tag?
It's messing the page layout...
Thanks...
Cássio Landim Ribeiro
The wrapping markup used can be set via methods in AbstractLink:
setAfterDisabledLink()
setBeforeDisabledLink()
or, you can set a default at application level:
setDefaultAfterDisabledLink()
setDefaultBeforeDisabledLink()
Cassio wrote:
Hello everybody!
Does anyone know for what reason an
But it would change only the em and /em default markups and not the
span that replace the a tag at
org.apache.wicket.markup.html.link.AbstractLink.disableLink(final
ComponentTag tag) method.
code:
// Change anchor link to span tag
tag.setName(span);
2009/7/24 Iain
