[
https://issues.apache.org/jira/browse/MYFACES-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021801#comment-13021801
]
Werner Punz commented on MYFACES-3113:
--------------------------------------
The issue here is the onclick handler of the event decorator, not my code. The
question is does Mojarra behave the same and if yes, is this really a bug or
more along the lines of a spec issue.
The workaround is simply to use jsf.ajax.request directly instead of f:ajax
then you have full control on the keyup handling.
> F:ajax events deliver a bit too much (e.g. for "keyup" it already delivers
> the KEYUP when you tab into a field that has <f:ajax even="keyup" ... />
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-3113
> URL: https://issues.apache.org/jira/browse/MYFACES-3113
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.5
> Reporter: Matthias Weßendorf
> Priority: Critical
>
> IMO the <f:ajax> delivers a bit too much.
> For instance, take "keyup":
> it already delivers the KEYUP when you tab into a field that has <f:ajax
> even="keyup" ... />
> I was not expecting that - not sure if the SPEC is silent.... but the
> behavior is odd (especially when tabbing into the "ajaxified" field
> (also there is no way to restrict the actual list of KEYs (e.g. filter on
> number keys)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
