Tapestry
  1. Tapestry
  2. TAPESTRY-810

Radio components don't have unique client id's

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      any

      Description

      Because Radio components don't generate id="" html attributes, it becomes almost impossible to do standard client side interactions with them. An easy fix would generate unique id's based on the option value + groupname for the unique id.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            Jesse Kuhnert
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development