[
https://issues.apache.org/jira/browse/TAP5-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187002#comment-15187002
]
Jochen Kemnade edited comment on TAP5-2225 at 3/9/16 12:49 PM:
---------------------------------------------------------------
-What if we just skip the check against the safe character set when *decoding*?
We could still keep the special handling for blank and null values in place.
But I don't see a need to enforce the dollar encoding for incoming URLs.-
Sorry, I commented on the wrong issue.
was (Author: jkemnade):
What if we just skip the check against the safe character set when *decoding*?
We could still keep the special handling for blank and null values in place.
But I don't see a need to enforce the dollar encoding for incoming URLs.
> Create client-side API to call a component's event handler methods
> ------------------------------------------------------------------
>
> Key: TAP5-2225
> URL: https://issues.apache.org/jira/browse/TAP5-2225
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Jochen Kemnade
> Assignee: Thiago H. de Paula Figueiredo
> Labels: ajax, event, handler, javascript
>
> It should be possible to create URLs for components' event handlers on the
> client side.
> There could be a function that mirrors the behavior of
> ComponentResources#createEventLink. It might be passed an event name or an
> object with additional information such as a page name, a request context, or
> additional request parameters.
> The function could either return the URL or a function that makes an XHR and
> passes the response to a callback.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
