Ok, I guess I don't understand what the problem is. When you say "dead space" what do you mean? You have a scrollable frame on your page and you are trying to swipe to the next article? Is the scrollable frame set to "vertical only"? You are *positive* it is a JPEG format article and not PDF?
i am ***positive*** about the JPEG article. however the dead space i am talking about is the container frame's "framework" which houses my content frame (pullout tab). it creates a dead space that you are unable to use to flip to the next page. my pullout tab is on the right hand side of my article and therefore it's the most likely point right handed people will scroll from, BUT that entire space opens my (majority hidden) tab rather than move onto the next page. and no, my scrollable frame is set to horizontal only.
Try experimenting with an invisible dummy MSO you lay over the scrollable frame area. Swiping from the tab still opens the pull tab, and swiping to the left of the tab browses to the next article. Just cover a middle portion of the area -- you don't want users to get stuck when they pull out the tab, release it, and try to drag it back.
That's exactly what I just did. I'm having to experiment with the faux
button area though because initially it would cause my tab to get stuck
after it was pulled out. It's still a work around though. It would be nice
if this was recognized as the real problem that it is with a fully
functioning solution. But thank you for all your help. I appreciate your
Sent from my iPhone
I think I have had the same problem. I created two horizontal pull out tabs, the first one was the largest content frame, taking up a full half of a page vertically, and contained a vertically scrollable frame within. It was set behind the second frame which took up the full width of the page but only the lower quarter. I discovered two things: the upper, smaller content frame made the vertical scrollable frame within the other content frame have a smaller 'scrollable area' so you could only scroll where the other frame didn't exist (even though it is not visible). Also, the whole page navigation (moving from page to page, either up/down or sideways) was now limited to a small area in the top left corner where neither content frame existed. Needless to say the client was not happy and they have now become object states instead in order to maintain use of the whole page for navigation, as most people would use the lower right corner to swipe.