I've continued my "investigation" and found something interesting.
Here's an example pic of a mobile's app page: <http://qooxdoo.678.n2.nabble.com/file/n7586126/1.png> You can see a navigation bar on top, then here goes the content and then there's two elements (button and toolbar) added to root via this.add(). In this example content fits perfectly and there's nothing to scroll so the page is not scrollable. Here's a 2nd pic: <http://qooxdoo.678.n2.nabble.com/file/n7586126/2.png> Page's size is decreased and content doesn't fit. I've marked the image's area so that you can see that it's hidden by the button BUT in the same time it doesn't go outside of the complete page's size. Scroll have to be enabled but it's impossible to scroll. Here goes the most interesting part: if only I resize the window (even by 1 pixel) the scroll begins to work! My only idea is: During the page build process soon after building of the content part is finished it's scroll status is refreshed and if content fit's the page (and it fits indeed) then scrolling is disabled. After it some elements are added to the root, overlaying the content part, but scroll is not refreshed. After resizing of the page it refreshes and detects that some part of content is not visible, so scrolling is enabled again. Am I right and is there any possible fix for it? Can I manually call this "scroll refresh" from my initialize method so that it's refreshed after the page building is completed? Please, I really need an advise :) Thanks! -- View this message in context: http://qooxdoo.678.n2.nabble.com/Scrolling-and-zooming-on-different-mobile-devices-tp7585347p7586126.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
