myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Winer" <>
Subject Re: [Trinidad] tr:inputText required="true" silently blocks submission
Date Fri, 06 Jul 2007 23:22:00 GMT
If you remove simple="true" from the inputText, what happens?
Or, if you set an "id" on the tr:inputText and add a tr:message
component, what happens?  simple="true" means
there's no implict message component in the content.

My suspicion is that the client-side validation is trying
to show the error message inline, failing to find anywhere
to write the message, and just swallowing it.  We
could either:
  1. show these messages as JS alerts
  2. show these messages in some other block of content,
    picked perhaps arbitrarily  (in tr:messages by default,
     otherwise at the head of the page?)
  3. blow off client-side validation altogether for those elements

-- Adam

On 7/6/07, noah <> wrote:
> 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=""
>    xmlns:ui=""
>    xmlns:f=""
>    xmlns:h=""
>    xmlns:tr="">
>   <tr:form>
>       <tr:messages />
>       <h:outputText value="Foo=#{}" />
>       <tr:inputText required="true" simple="true"
> value="#{}" />
>       <tr:commandLink text="foo">
>          <f:setPropertyActionListener target="#{}"
> 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?

View raw message