Tapestry
  1. Tapestry
  2. TAPESTRY-165

Allow control over attribute name for components in templates

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.3, 3.0, 3.0.1, 3.0.2, 4.0
    • Fix Version/s: 4.0
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      Operating System: All
      Platform: All

      Description

      From a discussion in the newsgroup I would like to request a feature. That
      feature would be to change the way Tapestry embeds its tags from:

      <span jwcid="insertStuff">this gets replaced</span>

      To (something like this):

      <span tap:jwcid="insertStuff">this gets replaced</span>

      This allows for several things to happen. The first is that Tapestry now
      create XHMTL compliant templates at EDIT time so that developers and HTML
      coders can validate the XHTML. The second is more nebulous. But I believe the
      change to using a namespace would allow Tapestry more flexibility as future
      HTML changes come down the pipe to ensure Tapestry meets those specifications.

      Howard: What we really want is the ability to control the exact id, so that people can use 'id' (if they like), or
      use whatever namespace is convienient for them.

        Activity

        Robert Hicks created issue -
        Serge Knystautas made changes -
        Field Original Value New Value
        issue.field.bugzillaimportkey 28548 22672
        Howard M. Lewis Ship made changes -
        Component/s Framework [ 11280 ]
        Component/s Build [ 11284 ]
        Environment Operating System: All
        Platform: All
        Operating System: All
        Platform: All
        Fix Version/s 3.1 [ 10794 ]
        Priority Major [ 3 ]
        Assignee Tapestry Developer List [ tapestry-dev@jakarta.apache.org ]
        Description From a discussion in the newsgroup I would like to request a feature. That
        feature would be to change the way Tapestry embeds its tags from:

        <span jwcid="insertStuff">this gets replaced</span>

        To (something like this):

        <span tap:jwcid="insertStuff">this gets replaced</span>

        This allows for several things to happen. The first is that Tapestry now
        create XHMTL compliant templates at EDIT time so that developers and HTML
        coders can validate the XHTML. The second is more nebulous. But I believe the
        change to using a namespace would allow Tapestry more flexibility as future
        HTML changes come down the pipe to ensure Tapestry meets those specifications.
        From a discussion in the newsgroup I would like to request a feature. That
        feature would be to change the way Tapestry embeds its tags from:

        <span jwcid="insertStuff">this gets replaced</span>

        To (something like this):

        <span tap:jwcid="insertStuff">this gets replaced</span>

        This allows for several things to happen. The first is that Tapestry now
        create XHMTL compliant templates at EDIT time so that developers and HTML
        coders can validate the XHTML. The second is more nebulous. But I believe the
        change to using a namespace would allow Tapestry more flexibility as future
        HTML changes come down the pipe to ensure Tapestry meets those specifications.
        Bugzilla Id 28548
        Type Bug [ 1 ] Improvement [ 4 ]
        Howard M. Lewis Ship made changes -
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship made changes -
        Affects Version/s 3.1 [ 10794 ]
        Affects Version/s 3.0 [ 10792 ]
        Affects Version/s 3.0.2 [ 11063 ]
        Affects Version/s 3.0.1 [ 10793 ]
        Affects Version/s unspecified [ 10790 ]
        Summary Adding a namespace for the Tapestry tags Allow control over attribute name for components in templates
        Affects Version/s 2.3 [ 10791 ]
        Description From a discussion in the newsgroup I would like to request a feature. That
        feature would be to change the way Tapestry embeds its tags from:

        <span jwcid="insertStuff">this gets replaced</span>

        To (something like this):

        <span tap:jwcid="insertStuff">this gets replaced</span>

        This allows for several things to happen. The first is that Tapestry now
        create XHMTL compliant templates at EDIT time so that developers and HTML
        coders can validate the XHTML. The second is more nebulous. But I believe the
        change to using a namespace would allow Tapestry more flexibility as future
        HTML changes come down the pipe to ensure Tapestry meets those specifications.
        From a discussion in the newsgroup I would like to request a feature. That
        feature would be to change the way Tapestry embeds its tags from:

        <span jwcid="insertStuff">this gets replaced</span>

        To (something like this):

        <span tap:jwcid="insertStuff">this gets replaced</span>

        This allows for several things to happen. The first is that Tapestry now
        create XHMTL compliant templates at EDIT time so that developers and HTML
        coders can validate the XHTML. The second is more nebulous. But I believe the
        change to using a namespace would allow Tapestry more flexibility as future
        HTML changes come down the pipe to ensure Tapestry meets those specifications.

        Howard: What we really want is the ability to control the exact id, so that people can use 'id' (if they like), or
        use whatever namespace is convienient for them.
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Status In Progress [ 3 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Mark Thomas made changes -
        Workflow jira [ 32667 ] Default workflow, editable Closed status [ 12567064 ]
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12567064 ] jira [ 12589805 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development