Would someone please explain to me why transitioning between 2 divs within the viewport requires a scroll to the top of the page before transitioning? What is the constraint that jQM is having to deal with?
I have 2 page/pane divs within the body/viewport which are set up so that they each have independent scrolling positions and can transition ( slide ) between each other without having to call window.scrollTo():
I've taken a look at both the the splitview and multiview plugins that are available for tablet/iPad layouts. I would like to propose a simpler splitpage plugin that doesn't require changes to the jQM core ( like splitview ) and not as ambitious as multiview (I need something that works as of yesterday ).
The splitpage plugin is a container for a 2 pane page, where the page is divided vertically ( page is unfortunately not termed a view ). Each pane contains a page. The LH page is the navigation pane or master pane and the RH page is the detail pane.
The initial implementation will be only for the iPad with iOS 5.
AJAX loadPage() currently only processes the first page and ignores the rest of the page stack ( multiple divs with data-role='page' ). I needed to have a way to add subpages for certain views generated by the server, so I came up with a simple subpage widget. Here is the link to the github repository if anyone is interested (until loadPage adds this functionality post 1.0 ):