Issue Feature Closed

#22708there is no good way to add inline JS to header from extensions (jsInline is liable to collisions)

Vladimir Podkovanov 05/25/10, 03:05 updated 02/20/14, 16:59

Description

There are several PAGE’s properties which allow to include user’s javascript:
includeJSlibs.[array]
includeJS.[array]
jsInline (->CARRAY)

while first 2 options allow including JS via any text key, jsInline requires number, it is understood as JS lines should be in order
but it is inconvenient in case you create an extension which provides 3rd party JS lib where should be added some inline JS code on every page in order to configure the lib. The only option to include inline config JS is inlineJS but it allows collisions because of numeric keys – any number could be occupied yet in another extension or in main page’s template

so is needed some new property to add inline JS from extensions to header

(issue imported from #M14469)

Reviews 0

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