Oddly though it’s not every page using the same scrollable content container layout. No amount of rotating and refreshing makes it work. When it happens the content appears to ‘stick’ where the page behaves as if there where no scrollbars at all – not on the page or the content area. It works fine even on an iPhone, but when running on an iPad more often than not (but not always – apparently it depends on the type of content) the content area will simply not scroll. To make this work I use absolutely positioned headers and footers (if used – typically for phone sizes only) using ‘fixed’ styling.Īll of this works great in desktop browsers and just about any mobile browser. The content area is wedged between the header and the footer (or the bottom of the document if there is no footer) and the content needs its own scroll functionality rather than what the built-in browser scrollbar provides. In typical mobile apps I create, I tend to have a header area, a content area and in some cases a footer area. I’ve run into problems with scrolling tags with iOS Safari on a number of occasions and each time, I end up wasting untold amounts of time.
0 Comments
Leave a Reply. |