You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/04/29 10:33:14 UTC

[jira] [Commented] (TAP5-2244) T5.4 tapestry-core integration test app3/renderpagedemo exhibits shady requirejs behavior

    [ https://issues.apache.org/jira/browse/TAP5-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984116#comment-13984116 ] 

Jochen Kemnade commented on TAP5-2244:
--------------------------------------

The problem is that {{DocumentLinker.addScriptElements(Element)}} is called twice, once via the normal page render request and once via {{PageDocumentGenerator.render(String)}}.

> T5.4 tapestry-core integration test app3/renderpagedemo exhibits shady requirejs behavior
> -----------------------------------------------------------------------------------------
>
>                 Key: TAP5-2244
>                 URL: https://issues.apache.org/jira/browse/TAP5-2244
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Chris Poulsen
>
> The error can be seen by  firing up the app3 from an editor and visiting /renderpagedemo  - The console error is: "TypeError: require is not a function".
> From the page source it seems that all the javascript for requirejs configuration/initialization is included twice in the page.
> This error can also be reproduced using the adjustments from TAP5-2239



--
This message was sent by Atlassian JIRA
(v6.2#6252)