Why "print $scripts" is in the footer? [#540192]

Comment #1

Jackinloadup CreditAttribution: Jackinloadup commented 24 August 2009 at 17:40

This is also an issue for the gmap module. For google maps to load the javascript must be in the head and not the footer.

As odd as this is it seems putting scripts in the head would be the safest option.

Other ideas?

Log in or register to post comments

Comment #2

mcrittenden CreditAttribution: mcrittenden commented 2 September 2009 at 20:33

It's generally recommended to put JS at the end of the page so that it won't be loaded until the rest of the page is finished, but seeing as this is conflicting with other modules, I'd also like it put in the header.

Log in or register to post comments

Comment #3

Jackinloadup CreditAttribution: Jackinloadup commented 12 October 2009 at 14:49

Maybe we could have a theme setting that would switch the placement of $scripts?

Thoughts?

Log in or register to post comments

Comment #4

rootwork

he/him

English

🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR

CreditAttribution: rootwork commented 22 October 2009 at 11:26

+1 on that

I like using the theme for content editing, so the out-of-the-box failure to render Google maps via location was pretty problematic. Instead of moving the $scripts printing to the top every time I update this module, it would be great to have an option to put it in one place or another.

By default, though, I think functionality should trump performance. So by default I think it should be at the top, with the option to put it at the bottom for performance, with the caveat that it might disrupt operation of Javascript rendering.