I am running into an issue on iPads using Safari that I am hoping someone can point me on the right direction on.
The aurelia application (azure backend api) is for a flight school and is used in iPads for doing training logs, pre-flight data entry, and post-flight data entry.
All this generally works fine. However, the iPads are also used with an Electronic Flight Bag (moving maps, navigation, etc…, which is pretty resource intensive), so the browser is put into the background during most of the flight, and is only refocused once the flight is over and they are finishing up time-cards, and flight logs.
Now what previously happened was the student would open browser back up to the app, but be to far away for a wireless network connection. I managed that by using the document onBlur event to check if the server can be hit (not just a network connection) and was able to reduce/resolve all the errors that would cause with connection/loss of connection/re-connection.
The error I am now trying to overcome is that it appears Safari is tombstoning the Aurelia app, and when the browser is brought back into focus if a form was left open it looks complete, form fields have the last entered values, but all the state data for the page model is lost.
Is there a lifecycle event in Aurelia that would capture this type of issue where I could check and try to rebuild the model, or perhaps redirect them?