1-- this is a tricky thing, because theoretically JS events can happen during page load, and we don't want to have to complicate our HTML putting guards in front of them all.
For example, if you click an expander link, you shouldn't get a function undefined error.

There are various solutions:
- (leave includes at front, as it is now)
- put in aforementioned guards (over-complex)
- put in stubs that wait for full page load (over-complex)
- suppress the errors (nasty)
- attach the Javascript event handlers dynamically, stop using inline JS (see #508 -- very time consuming)

So I kind of think leaving it as is is the best approach. This is not really a big issue, our JS is very lightweight, we're talking a few KB that has to load once into the users browser cache.

Ultimately #508 could happen, but that is beyond reasonable to implement unless we get a sponsor with deep pockets. I don't consider that a high priority as the payoff to work ratio is pretty poor, and it does hamstring support for third-party code quite a bit.

4- done

Splitting up.

Whoops, accidentally set 'fixed' tag, meant 'wontfix' tag -- the issues here will get separate tasks.