I would also try it with 1.4.4. And 1.4.2 seems "popular". ;)
I see enough complaints about things that don't work right in 1.4.5
that I think it is shaky.
You can search the Issues on GitHub to see what has been reported.
It is worth learning a bit about using GitHub Issues. Most open-source
projects use GitHub, and then if they tag things properly, it is easy
to see a bug list for a particular version.
I use 1.4.5 in a project, and I seem to recall having this problem myself.
I haven't touched the project in a while, but I just found this
magical incantation:
// Initialize any
fixed global toolbars
$(
"[data-role='header'],[data-role='footer']" ).toolbar({theme:'a'});
The thing is, I played with global toolbars outside of pages, but
then decided against. I forgot to take this out. The comment is
wrong, because you can see that it will set the theme option for
every header and footer, even in pages, as the selectors aren't
sufficiently selective.
So, as often happens, I have code that works by accident!
I think, though, the correct solution is to make sure you
explicitly name a theme on your headers and footers, one way or the
other. When you have headers/footers in pages, JQM plays games with
them, moving them in and out of the pages.
Problem is, only pages have themes. The document doesn't.