应用程序切换后,iPad 显示网站/应用程序的错误状态
我没有发现与我的问题相关的任何内容,也许我使用了错误的关键字。但让我解释一下:
我的 iPad 遇到了一个奇怪的问题。我们有一个小的 javascript 应用程序/网站,没什么特别的。它通过 UIWebView 在本机应用程序容器中运行。问题是:
当我们在外部 safari 窗口中打开链接(例如 pdf)并切换回应用程序(通过四指手势或按钮)时,有时(并非总是)我们会看到网站的旧状态(例如旧版本)应该隐藏的 div 容器)直到 iPad 重新绘制窗口(一秒钟左右之后)。重漆后一切正常,但在重漆之前我们发现有些问题。
我们无法重建问题。它有时会以某种方式发生。
对我来说,iPad 似乎会存储网站的屏幕截图,直到重新绘制 DOM,因为它不会侦听任何事件。有时iPad会存储错误的屏幕截图? 这是 iPad/Safari/UIWebView 的已知行为吗?或者确实是应用程序容器或网站中的某些代码有问题?
I found nothing related to my problem, maybe I use the wrong keywords. But let me explain:
I have a strange problem with the iPad. We have a little javascript app/website, nothing special. It runs in a native app container via UIWebView. The problem is:
When we open a link (e.g. pdf) in an external safari window and switch back to the app (via four finger gesture or the button) sometimes (not always) we see an old state of the website (e.g. an old div container that should be hidden) until the iPad repaints the window (after a second or something). After the repaint everything is ok, but until this repaint we see something wrong.
We cannot rebuild the problem. It occurs somehow sometimes.
For me it looks like the iPad stores a screenshot of the website until it redraws the DOM, because it does not listen to any events. And sometimes the iPad stores a wrong screenshot?
Is this a known behavior of the iPad/Safari/UIWebView? Or is really a problem with some code in the app container or the website?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我现在有时会通过手势使用 iPad 和 iPhone,这也引起了我的注意。尽管我还没有开发应用程序,但我经常看到这种情况发生。
不仅可以使用 uiWebView,还可以使用 Spotify 和 Spotify 等应用程序。汤姆汤姆。它总是等待一秒钟左右,然后正确地重新绘制应用程序,有时会出现应有的旧状态。
我想这就是 iOS 的工作原理,对此我们无能为力。
I am using an iPad and iPhone sometime now with gestures, and this is something that got my attention as well. Even though I am not yet developing apps, I see this happening al the time.
Not only with uiWebView but also with apps like Spotify & TomTom. It always waits for a second or so and then repaints the app correctly, with sometimes an older state then it should have.
I guess this is how iOS works, and nothing really can be done about it.