javaserverfaces-spec-public
  1. javaserverfaces-spec-public
  2. JAVASERVERFACES_SPEC_PUBLIC-1117

"value" attribute for "h:command*" components should be marked as "required"

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.1, 1.2, 2.0, 2.1, 2.2
    • Fix Version/s: None
    • Component/s: Components/Renderers
    • Labels:
      None

      Description

      Take a look at <https://maven.java.net/service/local/repositories/releases/archive/javax/faces/javax.faces-api/2.0/javax.faces-api-2.0-javadoc.jar/!/vdldocs/facelets/h/commandButton.html>, and also the same page for commandLink. In both cases, the "value" attribute is listed as not required. The spec must be modified to show that it is required.

        Activity

        Hide
        paul_dijou added a comment -

        I can understand for commandButton (since it's always generate a <input> tag and not a <button> tag, which is sad btw), but why also for commandLink? You should be authorize to nest an outputText (or several of them), or graphicImage, or any combo of those, inside a commandLink. No need for "value" in that case since those components would be the value inside the <a> tag generated.

        Show
        paul_dijou added a comment - I can understand for commandButton (since it's always generate a <input> tag and not a <button> tag, which is sad btw), but why also for commandLink? You should be authorize to nest an outputText (or several of them), or graphicImage, or any combo of those, inside a commandLink. No need for "value" in that case since those components would be the value inside the <a> tag generated.
        Hide
        nikolaj_a added a comment -

        Also, the browsers will render a default text, dependent on the browser and language of the user, if the value attribute is left out. This is most likely not the desired result, but there is already a fallback in case this attribute is left out.

        Show
        nikolaj_a added a comment - Also, the browsers will render a default text, dependent on the browser and language of the user, if the value attribute is left out. This is most likely not the desired result, but there is already a fallback in case this attribute is left out.
        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
        Manfred Riem added a comment -

        Setting priority to Minor

        Show
        Manfred Riem added a comment - Setting priority to Minor

          People

          • Assignee:
            Unassigned
            Reporter:
            Ed Burns
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 1 hour
              1h
              Remaining:
              Remaining Estimate - 1 hour
              1h
              Logged:
              Time Spent - Not Specified
              Not Specified