Form media lacks support for raw javascript

[Tareque Hossain]

Form media allows form exclusive css and js to be linked in a systematic fashion. But it lacks support for inclusion of raw javascript that are generated on a per form basis (e.g. initialization of TinyMCE). As a result widget creators have to append javascript to their rendered widget. This translates into bad html practice of including javascript at random points of the HTML file.

This situation can be resolved by adding a third media type: raw_js which can be included at a desired point in the template as {{ form.media.raw_js }}

[Tareque Hossain]

Suggested changes to django/forms/widget.py

[Tareque Hossain]

Modified regression tests to accommodate changes in form media

[Russell Keith-Magee]

I'm bikeshedding, but I'm not sure I'm a fan of raw_js as a name. There's nothing particularly 'raw' about it - it's just an embedded script rather thank a linked script.

[Tareque Hossain]

I would say its a perfectly valid argument! Here are some other names I thought about (given the existing form media titles are 'css' and 'js'):

'inline_js'
'embedded_js'
or just:
'javascript'

[Julien Phalip]

Closing as dupe of #13978, which, although newer, also takes care of inline css. I believe it's better to tackle both css and js at once to maintain some consistency.