But I’ve noticed that under iOS 13, browsers don’t run in the background. And not just if the browser isn’t the App that’s in focus. When having multiple tabs open in a browser, the tabs not in focus don’t run background processes.
I made a simple test page, that increments a counter once a second. Whenever I switch away from that tab, or switch to a different app, the counter stops incrementing. This happens in both Safari and Chrome.
From a design point of view, it seems like critical long running tasks should be running on the server, not in client javascript. But I don’t use EWA, so I could be wrong.
The more I think about it, an EWA session probably doesn’t even really hold the ttTable data. I’d guess that EWA is kind of like Remote Desktop, and that the “client” is just a display and UI I/O.
Does a Dashboard with an auto refresh interval set, automatically update on EWA?
That makes me think that there is more going on then just serving up a webpage with all the fields being form inputs that are passed to the server. Unless it’s the server’s processing (building the page, and processing the inputs), that is what runs so slowly.