You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2021. It is now read-only.
When a fixed header (bigger than the usual) is used with a data-id, the page is rendered with errors.
I've resolved the issue simply calling $.mobile.activePage.trigger('updatelayout') after page rendering.
The text was updated successfully, but these errors were encountered:
I can confirm this issue when using "oversized" headers as persistent toolbars.
But only, if the second page is shown the first time.
May this is caused by the changed markup order when using persistent toolbars.
At those pages, after the first navigation, the header-markup is appendedTo the content-markup
and it seems the header then could not find its closest ui-page to compute and give the page container the needed top-padding.
After reading @MauriceG his comment I figured the cause of the issue is most probably same as #4019
When you inspect the code of the fiddle you'll see that the content comes before the header in the html.
I've build a fiddle of a "bug" that I'm experiencing: http://jsfiddle.net/y4AXb/4/
When a fixed header (bigger than the usual) is used with a data-id, the page is rendered with errors.
I've resolved the issue simply calling $.mobile.activePage.trigger('updatelayout') after page rendering.
The text was updated successfully, but these errors were encountered: