Oxide

  1. Bug #1398941
  2. Comment #1

Comment 1 for bug 1398941

Revision history for this message
Olivier Tilloy (osomon) wrote :

I guess either of the first two options would work.

I don’t know about WebKitGTK, but I just tested QtWebKit and it doesn’t provide a default error page (nor does it provide a way for applications to set one). When loading e.g. "http://invalid/" with QtWebKit, we get two load events: load started, and then load failed.

Whenever we implement a default error page, it would be good to expose an API to allow applications to override it.