You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2013/02/28 08:35:12 UTC

[jira] [Commented] (TAP5-2053) Use of `transient` property in alert options breaks JavaScript processors

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

Jochen Kemnade commented on TAP5-2053:
--------------------------------------

The problem was addressed in commit 9cd1ca923e6ca5e0ed12ba2bcb883f672c331b16, but that renamed the property from "transient" to "ephemeral" in only that particular place and leaves all other places alone. This is at least confusing.
                
> 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