iPad Safari 中的框架集问题
首先,虽然我确实知道框架集有点旧,应该避免。但就我而言,我最近开始处理一个客户项目,并且进行重大更改的权利有限,例如将框架集转换为 iframe 代码......
话虽如此,这就是问题所在; 我有一个框架集,其中 3 行定义为 60,*,70
现在第二行高度是动态的,取决于内容。如果第二行高度较小,则页面显示正常,以便所有 3 个框架都能正确显示。但是,如果第二行高度增加,我将无法在 iPad 上完全看到第三行框架。 实际上我可以在纵向中看到它,但不能在横向中看到它,这就是我认为问题所在...即高度计算基于可见高度。
此外,在您考虑将框架集/框架转换为 iframe 之前,我已经过去尝试过,iframe 无法在 iPad(最新的 IOS 4.3)上使用 2 根手指滚动,
请帮助我。谢谢。
First of all, while I do understand that frameset is kind of very old and should be avoided. But in my case, i have recently started working on a client project and have limited rights to make major changes, like converting frameset to iframe code...
Having said that, here is the issue;
I have a frameset with 3 rows defined as 60,*,70
Now the 2nd row height is dynamic and depends on the content. The page displays fine if the 2nd row height is less so that all 3 frames are displayed correctly..If however, the 2nd row height increases, I am unable to see the 3rd row frame completely on the iPad.
Actually I can see it in portrait, but not in landscape, which is where I think the problem lies...i.e. the height calc is based on visible height..
Also before you think of converting frameset/frames to iframes, I have already tried that in the past and iframes do not scroll using 2-fingers on the iPad (latest IOS 4.3)
Please help me. Thank you.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
将 Iframes css
overflow:scroll
并用于横向使用$(window).width() > 768
[因为纵向宽度是 768] 只是我的 2 美分!Put the Iframes css
overflow: scroll
and for landscape use$(window).width() > 768
[as portrait width is 768] just my 2 cents!您应该创建 2 个样式表,每种模式 1 个:
http://matthewjamestaylor.com/blog/ipad-layout-with-landscape -portrait-modes 或 http://www.cloudfour.com/ipad-css/
you should create 2 stylesheets, 1 for each mode:
http://matthewjamestaylor.com/blog/ipad-layout-with-landscape-portrait-modes or http://www.cloudfour.com/ipad-css/
请注意:方向检测在 iPad 或 iPhone 上的框架集内的框架中无法正常工作 - 无论是在 javascript 还是媒体查询中:(
Beware : orientation detection does not work properly on iPad or iPhone in frames inside framesets - either in javascript or media queries :(