• Pierre Rossi's avatar
    Don't forward loading of error pages to the API layer · ede95c2a
    Pierre Rossi authored
    
    The fact that the error pages are HTML and get loaded through the
    same mechanism should be kept an implementation detail and not be
    considered as a new load in the API sense.
    Also implement HasErrorPage for good measure and remove an anoying
    warning from the demo browser.
    
    The issue of the url not being changed remains in the QML test (but
    it doesn't affect a typical browser-like UI since the user input is
    still there untouched in the address bar), just make sure that failure
    does not affect the later checks. It also seems like we have a focus
    problem somehow, but the test should probably use a click for that
    matter.
    
    Change-Id: Ib5e363981a11287fdf4bfe84b93c999d96ed8087
    Reviewed-by: default avatarJocelyn Turcotte <jocelyn.turcotte@digia.com>
    ede95c2a
examples.pro 260 bytes
TEMPLATE=subdirs
qtHaveModule(webengine) {
    SUBDIRS += webengine/quicknanobrowser
qtHaveModule(webenginewidgets) {
    SUBDIRS += \
        webenginewidgets/demobrowser \
        webenginewidgets/fancybrowser \
        webenginewidgets/markdowneditor