I'm having this issue as well. Has anyone written a work around, is there a way to trigger a manual reload of the header once the page is loaded?
Yes, having this issue too. Any workarounds or way to refresh so that they appear in the correct position?
This was fixed as of yesterday, I think. Please confirm by testing Alpha 4. This links in the footer of this page should verify the fix:
No. This is not fixed yet.
While the demo page you reference works and seems similar to the test code that Matt (he is our QA engineer) linked to under the heading "EXAMPLE" above, our test code still fails. I have updated the page of images to show the full sequence used to test this.
To reproduce this problem, open http://test.eldacur.com/JQM/bug.html in Safari on an iPhone4, iPad, Mac OS X 10.6, or Windows XP. Click on the "bar" link. Return to the first page either by clicking on the "foo" link or hitting the JQM "Back" button. The headers and footers will be positioned wrong. Our results are all shown on the http://test.eldacur.com/JQM/JQM-Fixed-Header-Bug.html page.
Reopening issue as it isn't fixed yet. Please note links attached by Brons.
I think I'm also seeing the same issue with my app, but it seems to only be triggered when going to a nested list and go back, it disappears on IOS but isn't actually gone, you can click it items in the navbar if you guess where it is, it just isn't visible. Anyone know of a quick hack to fix it? honestly this makes my app unusable until this can be fixed.
I am seeing the same issue in iOS 4.3 with the alpha 4.
It's rather odd, but I'm only seeing this issue on pages that have only a listview and non-text content in the page.
For example, I have a page with an and a
If either the next page or the first page have other content (e.g.
I'm not sure what fixed this, but some recent change (last several days) seems to have resolved this issue. I'm no longer seeing any problems.
So thank you to whoever fixed it unknowingly!
(I'm not going to close it since it's possible I was seeing a different issue than the previous comments)
Whatever unwittingly fixed it for philipkimmey has NOT fixed it for the original submitters.
Beta 1 (and several nightlies leading up to it) fixes this bug. Recommend closing, Matt.