-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Persistent headers and footers placed under content after transition #4019
Comments
@hanselsen Are you still experiencing with 1.1.0? If you do, could you please post a test page using the latest build with jsbin or jsfiddle to illustrate? Templates: http://jsfiddle.net/enxXQ/ or http://jsbin.com/acoruj/edit#html Thanks |
I'm seeing this issue on 1.1.0 and have constructed a basic test case here: http://jsfiddle.net/mpiotrowicz/ckcCN/3/ The header and footer are still fixed in my case after transition, however the header has moved in the HTML to be after the content, as described by hanselsen |
@mpiotrowicz thanks a lot for the jsfiddle. Which browser/device versions are you experiencing this with? |
@agcolom - I'm seeing it on my desktop using Chrome 18.0.1025.163 and Firefox 11, visible after the first page transition. |
Hi all, thanks for all your reactions. What should I do next?? o.O |
This also actually appears on the docs page for persistent toolbars - http://jquerymobile.com/test/docs/toolbars/footer-persist-a.html Is this the expected behavior? In my case, I transition to a page I've dynamically created, but that has the same fixed, persistent header as my origin page. After transition, my new page "content" is partially hidden by the header, and is impossible to scroll to, again due to the header |
Hey all, |
Does seem kind of breaking, i.e., renders the use of persistent headers and thus jquery mobile useless if you need/use this. Would like to see progress on this. |
1.1.1 was just released and this is not fixed, will be for a later version I suppose? (as it says Milestone: 1.1.1) |
Im looking into this today at summit |
…aced under content after transition - Header and footer were both being appended broke out to prepend header and append footer.
Hi there,
I tried to update my project from jqm 1.0.1 to 1.1RC2.
I'll descripte my scenario:
<div data-role="header" id="header" data-id="myHeader" data-position="fixed" data-fullscreen="true">
What has been changed that this is happening?
The text was updated successfully, but these errors were encountered: