Tapestry
  1. Tapestry
  2. TAPESTRY-1277

Select component requires a "value" binding even after an "id" binding has been specified

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Invalid
    • Affects Version/s: 5.0
    • Fix Version/s: 5.0
    • Component/s: None
    • Labels:
      None

      Description

      Some form components like TextField don't require you to bind the "value" parameter if you specify the "id" parameter.

      The Select component does not yet follow this T5 rule of thumb.

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        The code appears to be in place for this, so it should work. It should have worked back in 5.0.1. Are you sure your container had the matching property? I guess I'll add a test case to prove it works.

        Show
        Howard M. Lewis Ship added a comment - The code appears to be in place for this, so it should work. It should have worked back in 5.0.1. Are you sure your container had the matching property? I guess I'll add a test case to prove it works.
        Hide
        Daniel Gredler added a comment -

        I just tried this again, and it seems to work. Sorry about the false alarm!

        Show
        Daniel Gredler added a comment - I just tried this again, and it seems to work. Sorry about the false alarm!
        Hide
        Daniel Gredler added a comment -

        Marking as invalid, since this worked the second time I tried it. Probably a typo on my side.

        Show
        Daniel Gredler added a comment - Marking as invalid, since this worked the second time I tried it. Probably a typo on my side.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Daniel Gredler
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development