Details

    • Type: Sub-task Sub-task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1
    • Component/s: Framework
    • Labels:
      None

      Description

      This was initially addressed in case 626 http://issues.apache.org/jira/browse/TAPESTRY-626

      Justin's (who is a coworker of mine) real goal in that case was to be able to dynamically create an id for a form. We use that id for javascript functions and bug testing. His issue was that the framework was generating an ID as well and both were being written as attributes in the html. Howard's solution was to disallow informal id tags for Form components by making "id" a reserved parameter. I think what we were hoping for was for the framework to not write a generated id if we specify one, so that the FormSupportImpl's render method would look like:

      if(!_form.getBindingNames().contains("id"))

      { _writer.attribute("id", formId); }

        Activity

        Hide
        Jesse Kuhnert added a comment -

        The client id generation handling has been rewritten, I believe what you wanted has been implemented.

        Show
        Jesse Kuhnert added a comment - The client id generation handling has been rewritten, I believe what you wanted has been implemented.

          People

          • Assignee:
            Unassigned
            Reporter:
            Chris Norris
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development