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 ho
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
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 t
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 dow
