Issues with load progress indicator / Current URL is invalid!

[lahwaacz]

There are multiple issues with the load progress indicator when the network connection is not ideal:

• The URL for the tab is not updated until the server responds and the page starts loading (or the connection timeout expires). Until that happens, you can't yank the new URL (obviously) and closing the browser leads to loss of information. This happens with both the QtWebEngine and QtWebKit backends.
• With QtWebEngine, the load progress indicator in statusbar does not appear until the server responds, so it is rather tricky for the user to conclude that something is wrong with the connection and not the browser.

[lahwaacz]

Oh, the progress bar might actually be there, since the [top] [<tab>/<ntabs>] part is shifted to the left, but stuck at 0% which makes it completely invisible... Apparently QtWebKit always sets it to a positive value so it's visible. In any case, IMO a textual description like [Loading 0%] would be nicer for this corner case.

[tbodt]

It is true that there's a percent indicator in the title bar, but when I have qutebrowser in OSX full screen the title bar is invisible.

[lahwaacz]

I guess I could configure tabs.title-format to include {perc} as the first item, but it seems odd to me to provide status information in the tab (or window) title rather than in the statusbar.

[haasn]

cc @annulen re: URL not being returned by qtwebkit until the page either loads or times out

10:11 <haasn> it's just in this metaphysical state between clicking on a link and that link timing out that the current URL is invalid
10:14 <haasn> It also doesn't work for other things involving the page URL
10:15 <haasn> for example yanking, opening in an external program, or downloading
10:20 <The-Compiler> haasn: probably because Qt has emitted loadingStarted at some point, but still returns an invalid URL when asked what URL it is
10:20 <haasn> so you're suggesting this is a qtwebkit-internal behavior/issue?
10:22 <The-Compiler> well, qutebrowser could work around it, but I'd prefer if QtWebKit/QtWebEngine would handle it properly
10:22 <The-Compiler> there's a qutebrowser issue for it somewhere
10:24 <The-Compiler> https://github.com/qutebrowser/qutebrowser/issues/2176

[blueyed]

I am also seeing the "Current URL is invalid!" error when trying something like gu or go on a page that is still loading.
qutebrowser should be able to set the URL internally already I would assume.

[The-Compiler]

FWIW a good test case for the "Current URL is invalid!" error is https://www.google.com/csi which returns HTTP/1.1 204 No Content.

[VehementHam]

#5359 (comment)