tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-2382) Add support for disabling the namespacing of ids during a partial page render
Date Tue, 02 Sep 2014 22:22:22 GMT

     [ https://issues.apache.org/jira/browse/TAP5-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Howard M. Lewis Ship closed TAP5-2382.
       Resolution: Fixed
    Fix Version/s: 5.4
         Assignee: Howard M. Lewis Ship

> Add support for disabling the namespacing of ids during a partial page render
> -----------------------------------------------------------------------------
>                 Key: TAP5-2382
>                 URL: https://issues.apache.org/jira/browse/TAP5-2382
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>              Labels: ajax
>             Fix For: 5.4
> Tapestry traditionally has namespaced all ids generated during an Ajax partial page render
(the result of clicking a link, or submitting a form, that updates a Zone on the client).
The namespacing is the injection of a arbitrary string (a nanosecond timestamp, in hex) into
the middle of all ids. This ensures no name collisions on the client ... but it breaks other
features, such as rendering of validation errors for a Form nested inside the Zone.
> By disabling this feature, and allocating ids exactly the way they would be during a
traditional full-page render, some features (such as rendering validation errors) can be restored
... for simple pages!
> This feature should only be used as a last resort, since it can have unexpected consequences.

This message was sent by Atlassian JIRA

View raw message