I had a quick look at how we can detect that access was denied, and it
seems that the only difference with a normal load sequence (load
started, load committed, load succeeded) is that the HTTP status code is
always 0 for all events in the sequence.
A "load succeeded" event with an HTTP status
Discussed the design side of things with James, and his guidance is to
use the standard error page for this case, which should come for free
once oxide reports a failed load.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
It doesn't look like net::URLRequestFileJob does an access check or
handles that condition. However, net::FileProtocolHandler delegates an
access check to net::NetworkDelegate (via OnCanAccessFile), and it looks
like that can be used to fail the load.
I'll give it a try
** Also affects: oxide
Ignore that - this should result in a failed load already. I'll
investigate what's going wrong
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1503332
Title:
Blank
4 matches
Mail list logo
