[
https://issues.apache.org/jira/browse/TAPESTRY-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529406
]
geoffcallender edited comment on TAPESTRY-1753 at 9/21/07 5:07 PM:
--------------------------------------------------------------------
This is critical because it is so common to have validators:required on
PropertySelection. It has, for instance, broken around half of all screens in
the Tapestry JumpStart Max application. Anyone with production apps will be
blocked from using 4.1.3.
was (Author: geoffcallender):
This is major because it is so common to have validators:required on
PropertySelection. It has, for instance, broken around half of all screens in
the Tapestry JumpStart Max application.
> Client-side validation is broken for PropertySelection
> ------------------------------------------------------
>
> Key: TAPESTRY-1753
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1753
> Project: Tapestry
> Issue Type: Bug
> Components: Core Components
> Affects Versions: 4.1.3
> Reporter: James Gates
> Fix For: 4.1.4
>
>
> Matt Raible found this problem with the 4.1.3-SNAPSHOT release and reported
> it on the mailing list, but I didn't see a JIRA issue for it:
> http://www.nabble.com/Re%3A-Validation-and-CSS-with-4.1.3-SNAPSHOT-p12397222.html.
> The behavior is still there in this build.
> The client-side validation code produces an empty popup when you submit a
> form if the form contains a PropertySelection component with validators.
> Here's the example from Matt's message:
> <component id="countryField" type="PropertySelection">
> <binding name="model" value="countries"/>
> <binding name="value" value="user.address.country"/>
> <binding name="validators" value="validators:required"/>
> <binding name="displayName" value="message:user.address.country"/>
> </component>
> You get the blank popup even when the validation should pass (i.e., the field
> has a selected option). As a test I created an alternate required validator
> that decorates the markup but doesn't generate any validation on the client,
> and that one doesn't exhibit this behavior. The problem appears to lie
> either in changes to Dojo's "required" validation in this release or in how
> Tapestry is using it.
> Matt questioned whether Dojo client-side validation works with this
> component. It has worked in previous versions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
