Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: Components/Renderers
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      130
    • Status Whiteboard:
      Hide

      cat2 renderkitdoc sig size_medium importance_small

      Show
      cat2 renderkitdoc sig size_medium importance_small

      Description

      <h:message> and <h:messages> are a good start to place error-messages of
      form-validations somewhere, but its behaviour and attributes are very limited in
      what you can do with it. I noticed that you can't even define a stylesheet for
      the table itself when you set <h:messages layout="table"/>, but only for the
      <span>s within the <td>s of the table.

      It's hard to explain what one needs to be able to do better and which api is
      required to achieve this. I don't know which plans for this might be in queue
      for JSF 2.0 and I'm surely not the best to design the perfect api. But I have
      attached two screenshots to this issue where you can see which flexibility of
      error-messages is prevalent in the web and that JSF is just at the very
      beginning in this topic and much more features are needed.

      In short these are:

      • a way to check if any validation errors have occured
      • a way to access the error-message(s?) of a certain component-id
      • a way to get a list of all fields that threw a validation-error

      This shouldn't be solved by new jsf-tags, but by #

      {...}

      expressions.

      And regarding the table-layout I mentioned at the beginning, it is surely
      usefull to add a tableStyle and tableStyleClass-attribut to the api.

        Activity

        Hide
        rogerk added a comment -

        triage

        Show
        rogerk added a comment - triage
        Hide
        kithouna added a comment -

        Did Catagay ever respond to this? This issue has been open for some 7.5 years now. Maybe decision should be made about it?

        Show
        kithouna added a comment - Did Catagay ever respond to this? This issue has been open for some 7.5 years now. Maybe decision should be made about it?
        Hide
        rdelaplante added a comment - - edited

        Please look at OmniFaces o:highlight for some ideas on highlighting UIInput components and the associated labels when there is an error:

        http://showcase.omnifaces.org/components/highlight

        Web designers regularly expect me to be able to implement this type of highlighting functionality for validation errors and I think it should be built into the basic components. I shouldn't need OmniFaces to do this.

        Show
        rdelaplante added a comment - - edited Please look at OmniFaces o:highlight for some ideas on highlighting UIInput components and the associated labels when there is an error: http://showcase.omnifaces.org/components/highlight Web designers regularly expect me to be able to implement this type of highlighting functionality for validation errors and I think it should be built into the basic components. I shouldn't need OmniFaces to do this.
        Hide
        Ed Burns added a comment -

        Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

        Show
        Ed Burns added a comment - Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.
        Hide
        Ed Burns added a comment -

        Increase priority.

        Show
        Ed Burns added a comment - Increase priority.

          People

          • Assignee:
            Unassigned
            Reporter:
            martenlehmann
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: