Created attachment 173277 [details]
This is an automatic test that works with my internet connection. Maybe a change to the milliseconds is needed in the GObject.timeout_add function call.
I'm working on Browse (a Sugar/OLPC Activity) that uses WebKitGTK+ from Python.
I'm trying to fix a bug related with the Spinning Cursor. We want to show the Spinning Cursor while the page is loading and show the Normal Cursor when the load finishes. So, I'm checking the 'load-status' property by connecting the signal 'notify::load-status' to a callback and setting the Spinning Cursor for WebKit.LoadStatus.PROVISIONAL, WebKit.LoadStatus.COMMITTED and WebKit.LoadStatus.FIRST_VISUALLY_NON_EMPTY_LAYOUT status.
So, if I press Esc (that calls WebKit.WebView.stop_loading) when the status is WebKit.LoadStatus.COMMITTED, it changes to WebKit.LoadStatus.FAILED, the 'load-error' signal is emitted (I get a web_error.code 302 here), the 'load-status' changes to
WebKit.LoadStatus.FIRST_VISUALLY_NON_EMPTY_LAYOUT and the Spinning Cursor is shown again but the page is not loading anymore.
I'm asking here if this is a bug or not. Should the 'load-status' change to another status after WebKit.LoadStatus.FAILED? Is that OK? Is WebKit keep loading the page after a call to WebKit.WebView.stop_loading?
Thanks for your answers.
PS: I'm attaching a test case (not perfect, but it shows the strange behaviour)
It's unlikely that we'll be able to fix this since WebKit1 has been removed.