Remi, Thanks your for response. I'd still need to use an IFRAME though. What I need to display is some old, malformed, user-contributed HTML that the client has in their existing database. I either need to isolate it or filter it, and I was preferring to avoid the latter. Is there any reason that I should know why an an IFRAME won't work?
Thanks! On Tue, Jul 6, 2010 at 11:50 AM, Remi Grumeau <[email protected]>wrote: > > I was aware of multiple scrolling libraries (TouchScroll, iScroll) for > the iPhone/iOS due to its inability (???) to support overflow:scroll > > Right, since the only touch screen event is the finger scrolling dedicated > to the page scrolling itself > > > However, I was not aware (and I am looking for confirmation) that IFRAMEs > don't really work either. It appears that the iframe doesn't respect any > attempt to give it a fixed size and always just resizes itself to its > content. Am I correct on this? > > Same "problem" i think. > > > Is the only way to scroll an IFRAME to place it inside a block element > with the overflow CSS property set and then to use a lib like the > aforementioned? > > Yeap > Forget about the iframe btw, just a DIV with a scroll JS on it > > R. > > -- > You received this message because you are subscribed to the Google Groups > "iPhoneWebDev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<iphonewebdev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/iphonewebdev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en.
