[TYPO3-core] RFC #13758: Bug: page.jsInline / page.jsFooterInline may fail with config.removeDefaultJS=external

[Steffen Ritter]

This is an SVN patch request.

Type: Bugfix
Bugtracker references: http://bugs.typo3.org/view.php?id=13758

Branches:
TYPO3_4-3 & trunk


Problem:
page.jsInline and page.jsFooterInline are build from cObject-Array.
These may contain _INT objects.
INT-Objects are put as <!--INT_SCRIPT.[a-z0-9]*--> markers in content, 
and replaced before delivery by TSFE.

removeDefaultJS=external moves the inlineJS to an external file. If 
there are markers for INT-Objects in the inlineJS they are moved to 
external file too (where they never will be substituted).

The result is, that
a, the JS file will raise JS-Errors
b, the INT-Object JS is not present

This means:
INT-Object must not relocated to an external file, since this is not 
compatible with TYPO3 INT-object handling.

Solution:
Extract the markers before moving to external file and include 
INT-Objects still inline.


See attached patch

regards

Steffen

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: rfc13759-inlineJS.diff
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20100306/0ecf0c14/attachment-0001.txt>