Monitoring webProcessStatus and then doing a reload if the process is killed by the system is probably ok for most webapps, but this isn't great for a navigation app. What happens to the state of the current navigation if the render process is killed and the webview has to be reloaded?
Monitoring webProcessStatus and then doing a reload if the process is killed by the system is probably ok for most webapps, but this isn't great for a navigation app. What happens to the state of the current navigation if the render process is killed and the webview has to be reloaded?