Comment 4 for bug 1398941

The fix for this does change the behaviour of WebView.loadEvent in a way which would break applications that depend on the broken behaviour. However, as this API was only introduced in 1.3 and the browser isn't using it, I don't think there will be any consequences for doing this. I wonder whether we should backport it to both 1.4 and 1.3 so that we don't end up with people depending on this bug (which would mean that we would have to fix it by introducing yet another new signal, whilst we keep the existing signal broken)?