[ http://issues.apache.org/jira/browse/TAPESTRY-819?page=comments#action_12361349 ]
Leonardo Quijano Vincenzi commented on TAPESTRY-819: ---------------------------------------------------- The specific case I'm using these ID's for is for client-side component updating. Basically Tapestry would provide some kind of clear association of a server-side component and a client-side HTML id. I was using "components.XXX.id" as a way of uniquely specifying the name from Javascript, but I found out that those names weren't unique if the component was reused several times in the same page. I then used id paths (which seems to work ok on my Firefox browser). I'm just concerned that those paths could not be XHTML compliant. I get your point. I assumed that the original JIRA issue was about making Tapestry component id's XHTML compliant. I guess this one is invalid then. Now, is there a possible alternative to using TapestryUtils.convertTapestryIdToNMToken() for this kind of work? Specifically TAPESTRY-813. Although using this utility method could work as a workaround, creating lots of Javascript components using this method is a bit contrived / not clear for beginners. This is important for the Ajax guys. In any case I guess this actual bug is invalid and the other one could be implemented as an enhancement in 4.1 > $ signs in generated element names / ids are illegal in XHTML - in slashed > component names > ------------------------------------------------------------------------------------------ > > Key: TAPESTRY-819 > URL: http://issues.apache.org/jira/browse/TAPESTRY-819 > Project: Tapestry > Type: Bug > Versions: 4.0 > Reporter: Leonardo Quijano Vincenzi > Assignee: Howard M. Lewis Ship > Fix For: 4.0 > > $ signs in generated element names / ids are illegal in XHTML. The > auto-generation algorithm would need to change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
