Tapestry
  1. Tapestry
  2. TAPESTRY-550

IMarkupWriter should automatically filter out duplicate attributes when rendering an element

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0, 3.0.1, 3.0.2, 4.0, 3.0.5
    • Fix Version/s: 4.1.2
    • Component/s: Framework
    • Labels:
      None

      Description

      If IMarkupWriter was simply smart enough to ignore duplicate attributes (in a case-insentive manner, of course), then it would not be always necessary to reserve parameter names (if you could guarantee that a particular attribute was always rendered).

        Issue Links

          Activity

          Hide
          Jesse Kuhnert added a comment -

          See comments from other ticket.

          Show
          Jesse Kuhnert added a comment - See comments from other ticket.
          Hide
          Andreas Andreou added a comment -

          I think it's nice to have the reserved parameters list in the spec. Assuming that
          component documentation will soon be auto-generated, who will then users know which
          parameters are simply not allowed?

          On the other hand, I find more interesting exactly the opposite functionality:
          an IMarkupWriter that aggregates values for the same parameter name.
          Components that are decorated by ValidationDelegates can then solve issues like
          TAPESTRY-975 - those components could (conditionally ?) use this new (and a bit more
          expensive) writer.

          Show
          Andreas Andreou added a comment - I think it's nice to have the reserved parameters list in the spec. Assuming that component documentation will soon be auto-generated, who will then users know which parameters are simply not allowed? On the other hand, I find more interesting exactly the opposite functionality: an IMarkupWriter that aggregates values for the same parameter name. Components that are decorated by ValidationDelegates can then solve issues like TAPESTRY-975 - those components could (conditionally ?) use this new (and a bit more expensive) writer.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development