Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.2
    • Fix Version/s: None
    • Component/s: Components/Renderers
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      353
    • Status Whiteboard:
      Hide

      EGTop5 effort_moderate cat2 size_medium importance_large draft

      Show
      EGTop5 effort_moderate cat2 size_medium importance_large draft

      Description

      Currently the renderkit docs for input specify that in decode no further
      processing of a component should take place if it is readOnly or disabled.

      I'd like to propose that this get modified to only apply to "disabled".
      According to (http://www.w3.org/TR/html401/interact/forms.html#adef-readonly)
      readonly input elements cannot be modified by the user. However, they can be
      modified by a script and it IS submitted with the form.

      For example. You might have a standard "datepicker" JS component. I may attach
      a javascript datepicker to an inputText component. If I want only the
      datePicker JS to modify the inputtext then I would set it to "readOnly". This
      will restrict user modification of the field but allow Script modification.
      When this form is submitted I would expect JSF to process the date entered using
      the date picker JS just like it would a non "readonly" input element.

      The big difference between disabled and readonly is disabled elements are not
      submitted with the form.

      I would expect JSF to process 'readOnly" elements but not "disabled" elements.

      Mike

        Activity

        Hide
        rogerk added a comment -

        re-target

        Show
        rogerk added a comment - re-target
        Hide
        rogerk added a comment -

        For now re-target for 2.2.
        If time permits may revisit for 2.1.

        Show
        rogerk added a comment - For now re-target for 2.2. If time permits may revisit for 2.1.
        Hide
        rogerk added a comment -

        triage

        Show
        rogerk added a comment - triage
        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 to Major

        Show
        Manfred Riem added a comment - Setting to Major

          People

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

            Dates

            • Created:
              Updated: