[
https://issues.apache.org/jira/browse/TAP5-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085499#comment-14085499
]
Lance commented on TAP5-2360:
-----------------------------
If you've got javascript errors, you can't expect Tapestry to behave
rationally. I agree with Howard.
If your button actions aren't valid until the page has loaded... Why not wait
until the page has loaded to add the actions to the buttons?
Sounds simple to me.
> 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)
