[
https://issues.apache.org/jira/browse/TRINIDAD-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906911#action_12906911
]
Matthias Weßendorf commented on TRINIDAD-1906:
----------------------------------------------
if we decorate f:ajax (or provide a tr:ajax) there is still the issue with
vanilla JS call (jsf.ajax.request()).
Andrew, do you know if there is a ticket for the missing hooks?
I am also not really looking to add an tr:ajax and yes, replacing the
"request()" function is odd, but with that, folks can use jsf.ajax.request() on
a "natural" base, and they don't notice any surprise. But sure... there is a
downside for doing so.
Clearly: the JS API has limitations, and the real fix is that there should be
hooks.
I will keep this ticket open, does not hurt to have one more open item, IMO :)
> Client Validation igonred with <f:ajax> tag
> -------------------------------------------
>
> Key: TRINIDAD-1906
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1906
> Project: MyFaces Trinidad
> Issue Type: Bug
> Affects Versions: 2.0.0.3-core
> Reporter: Matthias Weßendorf
>
> Have a form like:
> ...
> <tr:form....>
> <tr:panelFormLayout>
> <tr:inputText id="ajax" label="Field 1:">
> <f:ajax event="change" />
> </tr:inputText>
> <tr:inputText id="ppr" label="Field 2:" required="true">
> </tr:inputText>
> </tr:panelFormLayout>
> </tr:form>
> ...
> Go to field1, type and TAB out:
> => An ajax request is queued and send down to the server
> In Trinidad (with autosubmit, instead of f:ajax) you'd see a warning that
> "Field 2" is required
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
