-
-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Echo / message error on load failures #672
Comments
Interesting, mine shows an error, says page could not be loaded after some time |
Status view is now updated to show when a page is loading. The renderer will try as long as possible, and eventually report an error message. There are no events that should overwrite the status until it is done. |
I find it hilarious that my interface is half in English and half in Greek :-D |
Thanks, that's already an improvement!
We can do a little bit better I think, consider this:
Run `follow-hint-new-buffer` and follow a hint in the background.
Notice that both the status view and the echo area report that they are
loading the buffer. This is redundant, plus the current buffer does not
display any meaningful status anymore.
I suggest the following approach instead: when the buffer loads, have
print-status display the regular status bar with (loading...) appended
before or after the URL. This way it's contextual to the buffer that's
actually loading.
Thoughts?
|
Ah, I see what is happening, that behavior with the background was not intended... :-D |
I don't understand your proposed solution, can you explain how that would fix the problem? The real issue is that the status message is currently tied to a window, and not a buffer |
My suggestion:
- Don't use print-status like you did on a buffer load.
- Instead, in the print-status function, get the load state of the
buffer and print it next to the URL
(we might need a new buffer slot for that).
By the way, I'm realizing that the current fix is going off topic: the issue is about
load _failures_, e.g. when there is not internet connection. Right now
we get buffers like "Internel WebKit error" which means little to the
user.
What we must do here is handle the load-failed signal.
|
print-status would still need to be informed by someone, that would have to be on buffer load. are you suggesting the following: print-status invoked in buffer load with no arguments |
Strange that it tells you "Internal Webkit Error". For me it says the service or servername could not be resolved (which is what is happening). |
print-status would still need to be informed by someone, that would have to be on buffer load. are you suggesting the following:
print-status invoked in buffer load with no arguments
print status default status formatter adds loading if a buffer is currently loading?
Yes!
|
Strange that it tells you "Internal Webkit Error". For me it says the service or servername could not be resolved (which is what is happening).
Indeed, I never had this message myself.
|
The following code:
Produces an error:
here is the relevant section of the API: I believe this is an error in cl-cffi-gtk, I do think we can handle it in cl-webkit ideas? |
I can reproduce. Can you report to
https://github.com/Ferada/cl-cffi-gtk/
?
|
I will try to report, and I will try the other cl-cffi-gtk as well, I want to do some more investigation first though |
BAM! |
Fantastic! Note for posterity:
|
OK! I will try to do that in the future! |
Fixed here: 9a96ff1 |
Recipe:
We need to tell the user that the page could not be loaded instead of doing nothing, since it's very confusing.
Ideally, the status view should keep the load status displayed since the echoed message is ephemeral.
The text was updated successfully, but these errors were encountered: