[jira] Commented: (TAPESTRY-2640) Javascript includes are rendered out of order for portlets

["Daniel Watson (JIRA)" <de...@tapestry.apache.org>]

    [ https://issues.apache.org/jira/browse/TAPESTRY-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628459#action_12628459 ] 

Daniel Watson commented on TAPESTRY-2640:
-----------------------------------------

I first noticed this when using a tacos @dojo:Widget component.  I guess it could be localized to tacos, but Its my understanding that the framework controls the render order of component contributed scripts.

> Javascript includes are rendered out of order for portlets
> ----------------------------------------------------------
>
>                 Key: TAPESTRY-2640
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2640
>             Project: Tapestry
>          Issue Type: Bug
>          Components: JavaScript, Portlet
>    Affects Versions: 4.1, 4.1.1, 4.1.2, 4.1.3, 4.1.5
>            Reporter: Daniel Watson
>            Priority: Critical
>
> The JavaScript includes are rendered out of order when building portlets using the <ScriptIncludes> tag.
> For example, when using a dojo tab widget within a portlet, the following script tag...
> <script type="text/javascript"><!--
> dojo.require("tapestry.widget.Widget");
> // --></script>
> ...is rendered before the <ScriptIncludes> tag is able to render the dojo configuration script, causing a "dojo is not defined" JavaScript error, since the dojo object does not exist.  This prevents the widget from being rendered.
> Id fix this myself, but I have no clue where the render decisions for JavaScript is made.

-- 
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org