[
https://issues.apache.org/jira/browse/TRINIDAD-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Robinson resolved TRINIDAD-94.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.2-core
tr:messages now participates in INLINE validation. Input components with
simple="true" will have their error messages appear in tr:messages. This
should match the standard server-side implementation.
> Inline JS validation fails silently when no location is available for a
> message
> -------------------------------------------------------------------------------
>
> Key: TRINIDAD-94
> URL: https://issues.apache.org/jira/browse/TRINIDAD-94
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.0.1-core
> Reporter: Adam Winer
> Assignee: Danny Robinson
> Fix For: 1.0.2-core
>
>
> In the following Facelets example:
> <tr:document xmlns:tr="http://myfaces.apache.org/trinidad";>
> <tr:form>
> <tr:messages />
> <tr:inputText required="true" simple="true"/>
> <tr:commandLink text="foo"/>
> </tr:form>
> </tr:document>
> ... clicking the link will silently fail until a value is entered. If
> simple="false", you see the error message
> appear. This is because the inline JS validation code just drops a message
> when there is no target
> to display it.
> We should do one of:
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
