You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "yiannis pericleous (JIRA)" <ji...@apache.org> on 2014/08/04 16:51:13 UTC

[jira] [Reopened] (TAP5-2360) Floating console appears in production mode

     [ https://issues.apache.org/jira/browse/TAP5-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

yiannis pericleous reopened TAP5-2360:
--------------------------------------


The console comes up when users click on links while the page is still loading, resulting in javascript errors (happens mostly with slow connections and old IEs). The floating console then pops up. These javascript errors are out of my control.

Note: the floating console does not pop up in all js errors, only in certain cases. One case is the one in the description of the ticket. I believe it comes up if there is a js error before the page is loading.

The statement 'Don't have javascript errors' does not make the problem go away. This is a valid tapestry issue that should be looked at. The floating console should NEVER come up in production, or at least have an option to completely disable the console. 

thanks

yiannis

> Floating console appears in production mode
> -------------------------------------------
>
>                 Key: TAP5-2360
>                 URL: https://issues.apache.org/jira/browse/TAP5-2360
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: yiannis pericleous
>
> The floating javascript console appears in IE if there are javascript errors for requirejs in the page and tapestry.production-mode=true in web.xml. It should only appear in dev mode.
> To reproduce (I tried this in IE 8 and 9):
> web.xml:
> tapestry.production-mode = true
> In a page.java:
> javascriptSupport_.require("test");
> test.js:
> (function() {  define([], function() {
> 	  aaaaaaa;
> })}).call(this);
> using 5.4-beta-6



--
This message was sent by Atlassian JIRA
(v6.2#6252)