Re: "Warning from Netsurf: Unknown"
Vincent Sanders wrote on 4 Nov: > I have changed how all network errors are reported to be a proper error > page instead of a popup. please can those affected (using CI builds) > confirm that the new behaviour is more informative and works for them. Thanks for that welcome change, Vincent. I downloaded and installed #4881 just now and tried the site that I first reported in this thread. I now get a "Connection timed out" error page -- screenshot here : http://archivemag.co.uk/TEMP/NS-timedout.png (45K) But I'm not clear whether this page came from Netsurf or from the site named in the URL bar of the page. If Netsurf, could I suggest that your design say so? (Maybe just add a Netsurf logo.) Anyway, it *is* more informative! Cheers. -- Jim Nagelwww.archivemag.co.uk
Re: "Warning from Netsurf: Unknown"
On 4 Nov 2019 "Richard Torrens (lists)" wrote: > In article <20191104112318.oax3l5xs43fqr...@kyllikki.org>, >Vincent Sanders wrote: >> I have changed how all network errors are reported to be a proper >> error page instead of a popup. please can those affected (using CI >> builds) confirm that the new behaviour is more informative and works >> for them. > Nice one! > Yes, the error "Couldn't resolve host name" is reported nicely. And here with CI 4881. Many thanks. Best wishes, Peter. -- Peter Young (zfc Hg) and family Prestbury, Cheltenham, Glos. GL52, England http://pnyoung.orpheusweb.co.uk pnyo...@ormail.co.uk
Re: "Warning from Netsurf: Unknown"
In article <20191104112318.oax3l5xs43fqr...@kyllikki.org>, Vincent Sanders wrote: > I have changed how all network errors are reported to be a proper > error page instead of a popup. please can those affected (using CI > builds) confirm that the new behaviour is more informative and works > for them. Nice one! Yes, the error "Couldn't resolve host name" is reported nicely. -- Richard Torrens. http://www.Torrens.org for genealogy, natural history, wild food, walks, cats and more!
Re: "Warning from Netsurf: Unknown"
On Tue, Oct 22, 2019 at 01:21:26PM +0100, Richard Porter wrote: > On 22 Oct 2019 David Pitt wrote: > > > It is on the bug tracker now. The example above is a very broken site, > > neither Safari or Firefox get anywhere with it. > > I get the same response after a long wait. > I have changed how all network errors are reported to be a proper error page instead of a popup. please can those affected (using CI builds) confirm that the new behaviour is more informative and works for them. -- Regards Vincent http://www.kyllikki.org/
