feat: webViewWebContentProcessDidTerminate: start at root path or document the current behavior

[hermitdemschoenenleben]

Feature Request

Description

For quite some time, we noticed weird errors in our error logs that we couldn't explain. After some debugging we found out that sometimes our ios app doesn't start at / path but at some subpath. This was quite surprising for us as we expected that mobile apps always start at / path. After a while we found out that webViewWebContentProcessDidTerminate followed by webView.reload() is the culprit here.

We've spent quite some time on debugging this issue and as there are some threads on stackoverflow discussing this topic, others probably have been doing so as well.

I'd like to propose two solutions for this:

• webViewWebContentProcessDidTerminate could do webView.load("/"). This would result in a completely normal, clean app start, which is the least confusing behavior in my opinion.
• I do understand the approach of "restoring as much state as possible", though. If you think it's better to reload the webview at the current path, I think it would help a lot if this behavior was documented somewhere: a warning that developers shouldn't expect the app to always start at / would help a lot.

Platform(s)

ios

Preferred Solution

After webViewWebContentProcessDidTerminate load the webview at / instead of reloading it at the current path.

Alternatives

Alternatively, document the current behavior.

Additional Context

#2379