The value of getClientId() seems critical to the proper use of client side javascript. However, unless a component includes a call to renderIdAttribute() while rendering its open element tag, the component seems unable to display its id property. I ran across this when i tried to use an Image as a target for an @EventListener. I suspect that it effects other components as well.
By default Image doesn't render its ID and if you tried to set id="clientId" as an informal parameter then you run into a stack overflow because the ClientIdPropertyWorker checks the component's "id" binding. This doesn't seem to be a huge issue because you can simply wrap the image component with an Any component. However, it does seem inconsistent and results in superfluous wrappers. Before I add this to the jira with a patch - i just wanted to make sure I didn't miss something. Carlos -- View this message in context: http://www.nabble.com/image-doesn%27t-render-id-tp16096885p16096885.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
