You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Fernando (JIRA)" <ji...@apache.org> on 2009/02/04 18:23:59 UTC
[jira] Commented: (TAP5-369) The position of included JavaScript
libraries (top or bottom) should be selectable per-page via meta data.
[ https://issues.apache.org/jira/browse/TAP5-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670381#action_12670381 ]
Fernando commented on TAP5-369:
-------------------------------
another nice to have dealing with script placement. Away to place scripts after Tapestry Init..
the current use case is I want to be able to initialize a zone (Tapestry.init.zone), but then activate the zone with javascript as soon as the page loads (to do delayed loading, etc), but at the moment it's hard to add script code after Tapestry.init runs.. even within Tapestry.init, you can't order the initializations to have interdependencies..
> The position of included JavaScript libraries (top or bottom) should be selectable per-page via meta data.
> ----------------------------------------------------------------------------------------------------------
>
> Key: TAP5-369
> URL: https://issues.apache.org/jira/browse/TAP5-369
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0.16
> Reporter: Peter Stavrinides
> Priority: Minor
>
> Sometimes it is necessary to be able to override the configured global default setting of "tapestry.script-at-top"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.