{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/500596b2173de37be9e388d43cf8f91f?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"500596b2173de37be9e388d43cf8f91f","url":"https://api.github.com/users/ChristianWeyer","login":"ChristianWeyer","id":888718},"labels":[],"assignee":null,"updated_at":"2011-11-15T10:37:04Z","comments":16,"closed_at":null,"url":"https://api.github.com/repos/frequent/bartender/issues/2","body":"I know that this seems to be an issue with the current jQM 1.0b3 build - all looks fine on desktop Chrome, on desktop safari, but jumps on iOS Safari.\r\nAny idea how to fix this?\r\n\r\nThanks.","html_url":"https://github.com/frequent/bartender/issues/2","title":"Persistent navbar jumps on iPhone device","number":2,"id":1724856,"created_at":"2011-09-23T16:42:44Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/430991b22a96d87c7880046590f22dbe?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"430991b22a96d87c7880046590f22dbe","url":"https://api.github.com/users/frequent","login":"frequent","id":729888},"updated_at":"2011-11-15T10:37:04Z","url":"https://api.github.com/repos/frequent/bartender/issues/comments/2743246","body":"Been a while, but I had jumpy navbars in my other plugin, too. \r\n\r\nI fixed it by hacking into JQM like this. \r\n\r\nHack 1:\r\n- in JQM look for this line: _//function for transitioning between two existing pages_\r\n- block this scrollTop:   _window.scrollTo( 0, $.mobile.defaultHomeScroll );_\r\n- block this scrollTop:   _if( !touchOverflow ){ $.mobile.silentScroll( toScroll ) }\r\n\r\nComment out the lines first to see if it works. If it does I would not block them altogether but put them in a wrapper to check for some condition. This made it almost work. \r\n\r\nHack 2 (more likely the cause):\r\nI think the faulty behavior is in the fixed toolbar function, hide(), show() and setop() functions.\r\n\r\nsoso explanation\r\n- think of a page with 2000px length and screenHeight: 500px.\r\n- plain footer will sit at the end of these 2000px. \r\n- fixed footer is shown by JQM by more or less setting it's position el.css(\"top\", to ~ -(2000px-500px) = -1500px (pull-up))\r\n- fixed footer is hidden by setting it's position to el.css(\"top\", 0); = end of the document (push-down)\r\n- if your page height is smaller than the screenHeight, say 250px, the computed show() position will be positive -(250px-500px) = 250px. But the repositioning function for the footer only takes negative values, so it will not be positioned correctly initially and get el.css(\"top\",0) = jump-up\r\n- the event fires at least two times and on the second run the wrong value is overwritten resulting in correct position.\r\n\r\nThere's the cause I believe. I fixed it in my plugin 99%. It still jumps up once on pageinit, but this is for an unrelated reason. Posting this to the issue so it hopefully will be solved.\r\n\r\nCheers\r\n\r\n","id":2743246,"created_at":"2011-11-15T10:37:04Z"}}