Code review comment for lp:~michael-sheldon/webbrowser-app/fix-1354388

That seems to work well, however I’m wondering if there isn’t a more general way to fix that, because in the case where there is no certificate error, opening the browser on a previously open page will still display a blank address bar for a short while.

Basically we need to set chrome.requestedUrl accordingly when the currently active webview starts loading, regardless of whether there is a certificate error. Not sure exactly where in the code this needs to be done though, I’d need to take a closer look.