tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ulrich Stärk (JIRA) <j...@apache.org>
Subject [jira] [Commented] (TAP5-2053) Use of `transient` property in alert options breaks JavaScript processors
Date Thu, 28 Feb 2013 07:45:13 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589307#comment-13589307

Ulrich Stärk commented on TAP5-2053:

I didn't notice that an issue already existed for this. Let me have a look at your patch and
see what can be improved.
> Use of `transient` property in alert options breaks JavaScript processors
> -------------------------------------------------------------------------
>                 Key: TAP5-2053
>                 URL: https://issues.apache.org/jira/browse/TAP5-2053
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Jochen Kemnade
>            Assignee: Howard M. Lewis Ship
>              Labels: javascript, patch
>         Attachments: 0001-transient-is-a-reserved-word-in-JavaScript-so-we-esc.patch
> The alert options use a property named `transient`. As that is a reserved keyword, it
breaks JavaScript compilers. This was already addressed in commit ff5cb2ea4d640c78ab7e2c14b47502f8bd3c8e73
but the fix got lost.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message