I have a very standard page setup with fixed header/footer and a content. Right now, if the content fits the screen space, no scrolling will occur and everything looks clean. However, when the content is larger than the screen space, user can start to scroll to view the content. However, it also provides an undesired effect of inertia scrolling on the header and footer. The header and footer need to be fixed to give a polished and native app experience.
This behaviour is also observed in the Kitchen Sink sample application.
I have a very standard page setup with fixed header/footer and a content. Right now, if the content fits the screen space, no scrolling will occur and everything looks clean. However, when the content is larger than the screen space, user can start to scroll to view the content. However, it also provides an undesired effect of inertia scrolling on the header and footer. The header and footer need to be fixed to give a polished and native app experience.
This behaviour is also observed in the Kitchen Sink sample application.
Essentially, we should deliver something similar to the flexbox layout in http://devblog.blackberry.com/2013/04/blackberry-10-ui-layout-patterns. I tried the flexbox sample codes on alpha device and the header/footer are indeed fixed.