I want to develop a simple webapp which will have a persistent footer navbar,
however, I do want to have some pages w/o that navbar.
While using JQM's I noticed a couple of problems:
1. When navigating from a page that does not have the navbar to a page that does, the navbar's position gets "recalculated" causing a UI glitch in my app (since it's created at the top of the page, right after the header) - causing an unwanted gap between the header the the content. [I've implemented a workaround* for this one, but still, I would prefer it being handled from within the platform]
2. Both iOS and Android seem to have problems rendering the navbar, flickering issues, cases where the navbar simply gets "stuck" in a certain position and the good ol' Houdini disappearing trick (which is rare, but happened more than once)
Did anyone came across these issues and managed to work around them / have a different idea?
* The workaround I've implemented is this:
Since I don't want a copy/paste code, I'm attaching to every page beforeshow event, looking for a specific DOM fragment (something that looks like this <div data-id=navbar></div>) which is then replaced by the proper JQM DOM fragement (at runtime), this is present in all pages of my app (including those that should not have one)
I'm adding a data-show="no" att. to each fragment that I don't want showing so when replacing my "placeholding" DOM fragment w/ the actual JQM fotoer DOM fragment I'm calling hide() the second it's created (I'm attaching to the ready() event of the "real" footer)