Ok, this is so bizarre, I don't know how to clearly describe it. I have a web app that I created years ago for managing a class I teach. It's a JavaScript app that runs on a single web page and changes the display property of one div element from "block" to "none" at the same time it changes the display property of another div element from "none" to "block" to simulate moving between different "screens" of the app when I click on navigation buttons. So basically, one div is hidden while another is made visible. For some reason, sometimes when the main div (the only one that is displayed when the app is loaded - shown in the two screenshots below) has been hidden and then later made visible again, Safari displays the web page like this:
It's supposed to look like this:
So do you notice that the top screenshot looks like I've dragged my finger partway down from the center of the screen to refresh the page, but stopped just short of triggering the refresh? But I haven't. Safari is literally doing this by itself. Once it does this, it's stuck like that forever until I actually do refresh the page. I can use the app, but that annoying space and wheel stay visible at the top of the page until I refresh. I cannot reproduce this consistently. It seems to happen randomly. Been running this app in Safari for years without an issue until now.
Anyone else have this happen to them?
If I figure out a way to consistently reproduce this, I'll update the thread.
It's supposed to look like this:
So do you notice that the top screenshot looks like I've dragged my finger partway down from the center of the screen to refresh the page, but stopped just short of triggering the refresh? But I haven't. Safari is literally doing this by itself. Once it does this, it's stuck like that forever until I actually do refresh the page. I can use the app, but that annoying space and wheel stay visible at the top of the page until I refresh. I cannot reproduce this consistently. It seems to happen randomly. Been running this app in Safari for years without an issue until now.
Anyone else have this happen to them?
If I figure out a way to consistently reproduce this, I'll update the thread.