Forum | Appery.io

I have a page with header and footer, page has a list populated from REST API (15 items) - all works great but I can't get persistent footer to work.

Issue:
when I scroll thru the list, footer stays fixed at the bottom of the screen but when I click on list item that is below visible area and navigate to other page it becomes an issue. I navigate back to previous page with footer and sometimes (not always) footer shows shortly after loading and disapears once list gets created from REST, sometimes it's gone right away - footer stays at the bottom of the list no visible on the screen - it doesn't reposition itself

sometimes it helps when I scroll my list few times up and down, footer shows up again as fixed.

I've tried full page refresh and ajax navigation when going back to this page from others, happens for both...

I checked JQM docs http://jquerymobile.com/demos/1.2.0/d... and added this line to my page but it doesn;t help when list exceeds the screen
$.mobile.touchOverflowEnabled = true;

Solution

• ??

• add "updatelayout" to tiggzi?

  This seem to be very common issue for native apps. Everyone in any project wants header and footer to be fixed and persistent, no exception

  Would it be possible to implement in tiggzi global solution for this?
  Could you test this issue? Just FYI this is possible reason for rejection in App Store, usability is broken

  Thanks

Which solution that you tried worked? Based on your post, it doesn't seem that anything worked?

correct, nothing seems t work 100%

mobile.touchOverflowEnabled works in most cases but when destination page has REST attached with list longer than screen it doesn't seem to work as well

also, it matters which events I use, seems like LOAD and PAGESHOW are worst, deviceready lets page to show (empty) and then trigger REST for smoothest transition - in any case slide transition (most native to iOS) breaks the process causing few reloads and white screens

So what exactly would you want us to do?

upgrade to the newest JQM version and test recommended by JQM team solution for persistent footer against REST requests triggered on different levels (load, page show, device ready etc) plus find global solution for what seems to be auto focus on long lists - I believe you will find some configurations that need to be avoided and preferred way to code

it appears to be critical for apple review approval process along with issues like most native transitions etc.

it would be great if tiggzi team could test these issues since all of them will affect all native apps, bottom line if every developer will have to test it on its own it will result in huge rejection rate and that's not good for tiggzi as well

there are things to avoid when creating apps for native devices and things that are recommended, it would be great to see blog posts for developers about that, sort of bst practices on coding level

this is great base for article/instructions how to create phonegap apps and possible corrections in tiggzi http://coenraets.org/blog/phonegap-tu... specifically page structure and transitions, tiggzi has issue with agressive cache that prevents user to use single page template and transitions when REST attached to a page

Tiggzi doesn't cache anything, it's the browser.

not sure why my post disapeared so I'm posting again

Max - I know that tiggzi doesn't cache : ) what I meant is that JQM used by tiggzi editor works with some sort of settings/pre-set architecture that is responsible for aggresive caching.

Developers follow the tutorial and hoping to create native app, they will waste their time without either proper tutorial targeting native apps and how to code for this type of apps or some sort of global implementation of native-standards

when you compare app created in tiggzi tutorial with article I pasted above, you will see that there is HUGE difference with approach, simply speaking I have no idea how and what to implement in tiggzi in order to get effects and smoothly working apps and I know it's possible with phonegap

Hello!

We cannot reproduse this problem: "footer shows shortly after loading and disapears once list gets created from REST".

Could you share your project with support@tiggzi.com, so we can test it?

shared - this issue doesn't happen in the browser as list creation based on REST happens when deviceready fires - when list longer than screen footer goes away randomly and comes back when any inactive area tapped