Hi Chris & Bob,
Thanks, yes, it's all part of the learning process. :-) Now that I know
that Tapestry ActionLink and EventLink only emit tags, I'll in future
style all my buttons as a.xxx rather than input.xxx (style.css).
I had wrongly assumed that Tapestry left the HTML markup as is, parsing
I think the EventLink component did the only thing it could reasonably be
expected to do. When you add t:type=foo to an HTML tag you're telling
Tapestry to change the tag to a foo component. In the case of
t:type=eventlink, the EventLink component emits an tag. That's the only
type of tag it knows
Hi Chris,
Yes, you were absolutely correct. Tapestry was changing my tags
to tags, and then of course the input.opto-button CSS code got totally
ignored. Modifying the CSS from 'input' to 'anchor' type wasn't so
trivial, particulary with vertically centreing button labels, which is
easy with '
