mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-10-22 12:05:37 +00:00
MINOR Documentation slightly improved for js inclusion
Although I'm not the best documentor.
This commit is contained in:
parent
892b772d1c
commit
5c595146a0
@ -139,11 +139,15 @@ to change inclusion-order, other than using *Requirements::clear* and rebuilding
|
||||
requirements. Caution: Inclusion order is both relevant for CSS and Javascript files in terms of dependencies,
|
||||
inheritance and overlays - please be careful when messing with the order of Requirements.
|
||||
|
||||
NOTE:
|
||||
By default, SilverStripe includes all Javascript files at the bottom of the page body. If this causes problems for you,
|
||||
### Javascript placement
|
||||
|
||||
By default, SilverStripe includes all Javascript files at the bottom of the page body, unless there's another script already loaded, then, it's prepended to the first `<script>` tag. If this causes problems for you,
|
||||
for example if you're using animation that ends up showing everything until the bottom of the page loads, or shows
|
||||
buttons before pushing them will actually work, you can change this behaviour through
|
||||
the `Requirements.write_js_to_body` configuration setting.
|
||||
buttons before pushing them will actually work, you can change this behaviour though.
|
||||
|
||||
With the `Requirements.write_js_to_body`, you can configure if the javascripts are written to the head (false) or body (true).
|
||||
|
||||
With the `Requirements.force_js_to_bottom`, you can enforce Silverstripe to write the javascript to the bottom of the page body, despite there being an earlier script tag. For example, when you have asynchronous scripts for Twitter earlier in your body (and stop speedtests from explaining about "scripts above the fold")
|
||||
|
||||
## CMS Requirements
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user