Something's fishy then...
I just double checked, very latest snapshot from maven:
http://tapestry.formos.com/maven-snapshot-repository//org/apache/
tapestry/tapestry-core/5.0.12-SNAPSHOT/tapestry-
core-5.0.12-20080428.110035-48.jar
Test.java:
package org.example.myapp.pages;
public class Te
Hi Steve,
I'm not seeing that behavior in 5.0.12-SNAPSHOT, at least with
pagelinks. When I don't provide a t:id, an id attribute is generated
based on the component name and subsequent instances use a rolling
scheme (pagelink, pagelink_1, etc). When I provide a component id
(slightly different fro
Upgrading from 5.0.6 to the latest snapshot, I found that all my
pagelinks and actionlinks defined in tml like this:
link
re no longer rendering with the clientid, ie.:
link
Instead, I get no id...
Same thing goes for pagelinks...
I can force the id to be rendered with:
link
but, that's k
