When the browser displays a certificate error, it indicates the request URL that the error originated from. This is fine - however, if the navigation is content initiated the addressbar will indicate the URL of the currently committed page (which will be different to the URL of the page causing the error).
I have an idea to fix this by navigating the webview to a placeholder interstitial page whilst waiting for a response from the browser. This will update the addressbar, keep the navigation history consistent and also make the back button behave the same as Chrome.
When the browser displays a certificate error, it indicates the request URL that the error originated from. This is fine - however, if the navigation is content initiated the addressbar will indicate the URL of the currently committed page (which will be different to the URL of the page causing the error).
I have an idea to fix this by navigating the webview to a placeholder interstitial page whilst waiting for a response from the browser. This will update the addressbar, keep the navigation history consistent and also make the back button behave the same as Chrome.