Relying on CSS that uses ids, rather than classes, will give you all kinds of issues integrating it all together. It may render faster on the client, I don't know.
It's possible to hook into Tapestry and "pre-register" all those ids that can cause conflicts. Tapestry will then not use them, and will dynamically allocate different ids; i.e., "header_0" instead of "header". On Fri, Apr 26, 2013 at 10:20 AM, Lance Java <lance.j...@googlemail.com>wrote: > I suggest that component authors use the code I gave you. I also suggest to > style by class instead of by id since the clientId should be a dynamic, > runtime value that is not known at build time. > > If components have a static clientId, they can not (legally) be used in a > loop. > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
