You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2012/12/16 02:46:16 UTC
[jira] [Commented] (TAP5-1887) Client-side JavaScript error if
console.info/debug/... is available but not a function
[ https://issues.apache.org/jira/browse/TAP5-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533246#comment-13533246 ]
Hudson commented on TAP5-1887:
------------------------------
Integrated in tapestry-trunk-freestyle #977 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/977/])
TAP5-1887: Client-side JavaScript error if console.info/debug/... is available but not a function (Revision a9433984c06dfe48ca28978e5245cc4a25eca87b)
Result = FAILURE
hlship :
Files :
* tapestry-core/src/main/coffeescript/META-INF/modules/core/console.coffee
> Client-side JavaScript error if console.info/debug/... is available but not a function
> --------------------------------------------------------------------------------------
>
> Key: TAP5-1887
> URL: https://issues.apache.org/jira/browse/TAP5-1887
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3.2, 5.3.3, 5.3.4, 5.4
> Reporter: Jochen Kemnade
> Assignee: Howard M. Lewis Ship
> Labels: fixed-in-5.4-js-rewrite, javascript, logging, patch
> Fix For: 5.3.5, 5.4
>
> Attachments: 0001-only-use-the-native-console-function-if-it-actually-.patch
>
>
> For example in IE8 there is console.debug, console.info and the like, but they are not real JS functions, so `call`ing them fails with an error, effectively aborting JS execution.
--
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