[
https://issues.apache.org/jira/browse/TAP5-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087767#comment-14087767
]
Jochen Kemnade commented on TAP5-2360:
--------------------------------------
But wouldn't that mean that we unconditionally require JavaScript enabled in
the browser to remove the div at the end of the initialization phase? Or would
you also create the div using JavaScript? Wouldn't that still leave a tiny
window where you could click the links before the blocker is created?
> 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)
