This sure feels like a mistake.
In the DOM and CSS worlds nodes can be selected by tag, class, and id. The Tapestry domain invents/requires yet another selector.
Personally I find this a source of much duplication. If you have a need to identify an element, better to use one "id" for all worlds - CSS, Javascript, and Tapestry. For elements where the id is needed only for Tapestry, a simple name convention could suffice to identify id's that should be stripped from the generated HTML.
My $0.02.
Howard Lewis Ship wrote:
Yes, to avoid the class.
4.0 lets you override which attribute to look for, so you can use id instead of jwcid (but then you can't set the id of your rendered elements).
-----Original Message----- From: Gregg D Bolinger [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 5:48 PM
Why does Tapesty use jwcid= instead of just looking for the id attribute and then verfying that against the .page specification as it does for the jwcid. Would it be harder to catch missing components early on? Just curious.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
