Tapestry
  1. Tapestry
  2. TAPESTRY-2388

The Any component should implement the ClientElement interface, and allocate a unique client id as necesssary

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.0, 5.0.11, 5.0.12
    • Fix Version/s: 5.0.12
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      It would be nice if the Any component implemented ClientElement, so that for example, mixing in arbitrary javascripts could be done so in a simple way (by injecting their container as a ClientElement, and getting the DOM id).

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        Thanks for the patch; I wrote my own that deferred allocating the id until the getClientId() method is first called.

        Show
        Howard M. Lewis Ship added a comment - Thanks for the patch; I wrote my own that deferred allocating the id until the getClientId() method is first called.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 5m
              5m
              Remaining:
              Remaining Estimate - 5m
              5m
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development