[
https://issues.apache.org/jira/browse/TAPESTRY-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship resolved TAPESTRY-2493.
--------------------------------------------
Resolution: Invalid
Assignee: Howard M. Lewis Ship
There are extremely valid reasons why putting JavaScript at the bottom of the
page, after all markup content, is a very good idea, both for compatibility
across browsers, and for overall rendering performance.
See http://developer.yahoo.com/yslow/faq.html
The problem is that you are emitting inline <script> blocks when you should be
using RenderSupport.addScript().
This is NOT going to change back.
> Javascript rendering at the end of pages is unacceptable
> --------------------------------------------------------
>
> Key: TAPESTRY-2493
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2493
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 5.0.13
> Environment: WinXP, J1.5.14, Jetty
> Reporter: Michael Gerzabek
> Assignee: Howard M. Lewis Ship
>
> With 5.0.13 all JavaScript libraries are now included at the end of the html
> page. This breaks many projects that use dynamic content rendering on the
> client!
> One example can be found in [1] resp. [2]. The behaviour makes it now a PITA
> to write components that have their own javascript files. Please - is there a
> solution to this?
> [1]
> http://www.nabble.com/Re%3A-T5-5.0.13-Javascript-rendering-at-end-of-document---questions-regd-to18110549.html#a18110549
> [2]
> http://www.nabble.com/T5-5.0.13-Javascript-rendering-at-end-of-document---questions-regd-to18110439.html#a18110439
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
