You should check your HTML with a syntax checker. But jsFiddle
does it for you. Just look for the red tags! (It can be confusing,
because it also colors attributes in dark red. Error tags are in a
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
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
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.
is a known issue persistent toolbars are also deprecated in 1.4.0 and
should be replaced by external toolbars.
issue is that the default theme is inherit, however during the
transition the toolbar moves outside the page and so has nothing to
inherit from. To fix this simply add a data-theme to your toolbars: data-theme="a".
I am very disappointed that persistent toolbars are deprecated in 1.4. I
will make an Issue to reconsider and un-deprecate them! (And keep them
in future versions.)
While external toolbars work well and are a nice solution for many
use cases, they are not good for others. If you have changing buttons
or other content in the toolbar on different pages or types of pages,
now you have to manage that. It is much easier in that case to use
An intermediate solution between the two is, for example, you have
different "sets" of pages each with a common toolbar. If it
is a small number of sets, you might create multiple external
toolbars, and enable only one at a time. I hesitate to mention this,
though, because I can imagine how it will be abused, LOL. (The same
way multi-page documents are abused...)
Leave a comment on watusiware's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic