Yes, and so if there are no scripts queued in header, it won't write head.js, but then if there are scripts queued in footer, it will write head.js in the footer. It should be writing head.js in the header regardless of where the other scripts are queued.

If you still don't understand what I'm saying:

If there are no scripts queued at all (none in header and none in footer), head.js isn't written, this works correct.
If there are scripts queued in both header and in footer, head.js is written in header, this works correct.
If there are scripts queued in header but none in footer, head.js is written in header, this works correct.
If there are scripts queued in footer but not in header, head.js is written in footer, this is the problem, head.js should be written in the header and then the head.js() call is only in the footer.

So, in the last example, with scripts queued in footer but none in header, it currently outputs:

<html>
<head>
</head>
<body>
...
<script type="text/javascript" src="head.load.min.js"></script>
<script type="text/javascript">head.js({script:script.js}, {script1:script1.s});</script>
</body>
</html>

When it should output:

<html>
<head>
<script type="text/javascript" src="head.load.min.js"></script>
</head>
<body>
...
<script type="text/javascript">head.js({script:script.js}, {script1:script1.s});</script>
</body>
</html>

Head.js being outputted in footer instead of head #5

Description

Activity

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions