I'm getting weird client side behavior with the tr:inputs. It seems to be connected to validation. The example below just has one required field, but I get the same behavior on larger forms when other validation rules are not satisfied.
<tr:document xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:tr="http://myfaces.apache.org/trinidad"> <tr:form> <tr:messages /> <h:outputText value="Foo=#{pageFlowScope.foo}" /> <tr:inputText required="true" simple="true" value="#{pageFlowScope.bar}" /> <tr:commandLink text="foo"> <f:setPropertyActionListener target="#{pageFlowScope.foo}" value="bar" /> </tr:commandLink> </tr:form> </tr:document> Anyhow, if the input field is blank clicking the link does nothing. No messages, nothing. If I switch to an h:inputText, the form submits and I get a message. Do I need to do something special to get messages from the client side validation that appears to be going on?

