Issue Bug Rejected

#78206Fluid ContainerViewHelper with jQueryNamespace="none" fail

Ralf Zimmermann 10/09/16, 16:24 updated 06/13/17, 12:05

Description

A setup with a backend module with a Fluid Template and this configuration

        <f:be.container
            enableClickMenu="0"
            loadExtJsTheme="0"
            loadJQuery="1"
            jQueryNamespace="none"
        >

will fail.
The expected behaviour is that a jquery script tag will be added to the html header and the “jQuery.noConflict(true)” inline javascript will not.

https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/fluid/Classes/ViewHelpers/Be/ContainerViewHelper.php#L110
https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/core/Classes/Page/PageRenderer.php#L1512
https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/core/Classes/Page/PageRenderer.php#L2241

This works but the DocumentTemplate adds the jQuery tag on each backend request to.

https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/backend/Classes/Template/DocumentTemplate.php#L630

The result is: 2 script tags and the jQuery.noConflict(true)” inline javascript

        <script src="/typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-2.2.3.js" type="text/javascript"></script>
        <script src="/typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-2.2.3.js" type="text/javascript"></script>
        <script type="text/javascript">
        /*<![CDATA[*/
        var TYPO3 = TYPO3 || {}; TYPO3.jQuery = jQuery.noConflict(true);
        /*]]>*/
        </script>
  • The “loadJQuery” parameter from the ContainerViewHelper is useless because the DocumentTemplate add this every time.
  • The jQueryNamespace=“none” parameter does not provide the expected result.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.