MyFaces Core
  1. MyFaces Core
  2. MYFACES-3113

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" ... />

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 2.0.5
    • Fix Version/s: None
    • Component/s: JSR-314
    • Labels:
      None

      Description

      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)

        Activity

        Hide
        Werner Punz added a comment -

        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.

        Show
        Werner Punz added a comment - 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.

          People

          • Assignee:
            Unassigned
            Reporter:
            Matthias Weßendorf
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development