On May 18, 2005, at 10:31 PM, Nick Westgate wrote:
Fair enough. Then I broaden my unintentionally narrow question. ;-)
Does anyone think it would be convenient if link components took another parameter ("disabledTag", say) that directed them to wrap their contents with a non-link tag and preserve informals?
I think it would be more consistent for disabled links to render a <span> if informal parameters exist.
But that is a rather tricky issue since informals for an active link would be different than informals on a <span> perhaps.
Erik
Cheers, Nick.
Richard Lewis-Shell wrote:
The "good reason" was probably one of compatibility/consistency with the
other link components.
Nick Westgate wrote:
Hi.
A minor issue this, but I'm emboldened by the LinkSubmit jira mails.
LinkSubmit renders as text when disabled, thus losing informal parameters like "class" or "style".
Is there a good reason why it doesn't instead output a span or other (user definable) tag in order to preserve "style" etc? Recently I hacked it to do just this, and it seems reasonable that the standard library component should do something similar.
Cheers, Nick.
-------------------------------------------------------------------- -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-dev- [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
