Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
5.0
-
None
Description
Tapestry needs an implementation of client-side field persistence. Ideally at least three new strategies:
client:page - store properties on the client as long as the containing page is the active page
client:app - store properties on the client indefinitely
client:form - store properties on the client, but only within forms, not within URLs (as query parameters)
Attachments
Issue Links
- is depended upon by
-
TAP5-9 Component event requests that fail should still send a redirect (to the exception report page)
- Resolved