[
https://issues.apache.org/jira/browse/TAPESTRY-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637444#action_12637444
]
Onno Scheffers commented on TAPESTRY-2364:
------------------------------------------
Hi Davor,
I'm glad you agree that we should be able to at least configure where the
scripts are inserted.
The problem with the solution you give here is that
1) It is a hack to get something working that is actually quite common behavior.
2) It makes the page visible only after all the resources are loaded or loading
and the scripts are all done running. This slows down page-loading instead of
making it faster, defeating the whole purpose of adding the scripts to the end
of the page.
I think we all agree now that it does make a difference if the scripts are
included in the head-section or at the bottom of the page and it may cause
problems for people.
If you look around at existing websites, nearly all of them have the scripts
included in the head section. It is the most common approach and therefore the
expected behavior for most people using the framework. Therefore I think the
default behavior should be to include those file in the head-section.
But if it is at least configurable, I'm happy.
> YSlow Recommendation: Write Scripts at bottom of page
> -----------------------------------------------------
>
> Key: TAPESTRY-2364
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2364
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0.12
>
> Attachments: sayHello.js, TestFast.html, TestSlow.html, TestSlow.html
>
>
> Tapestry is already doing a good job on this, by writing the dynamically
> generated <script> block at the bottom of the page, but the external scripts
> should also be down there.
> http://developer.yahoo.com/performance/rules.html#js_bottom
--
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]
