Open gabaum10 opened 9 years ago
Also, I was able to hack something by setting the CSS margin-top of the wrapper container to `-137, which appears to be the height of the header. Then, once the initial data load is complete, I set it back to 0 to restore the proper behavior. I was hoping not to have to keep an ugly hack like that in though. Maybe you can include something like that in the plugin to accomodate the weird jQM behavior?
I've noticed in using the plugin in jQM, when you first visit a page with scrollz enabled, the pull to refresh header is visible for a brief moment before disappearing. No matter where I put the .scrollz('hidePullHeader', true) I still get a flicker. Is there anything we can do about that?
I suspect it has something to do with the way jQM initializes their scroll behavior or something.