Both QDesktopWebView and QTouchWebView are emitting loadFailed for all sort of errors. This includes errors like the ones defined in Source/WebKit2/WebProcess/WebCoreSupport/qt/WebErrorsQt.cpp, which are private since their domain is "WebKit" and whose error codes are not exposed anywhere in our API. We should filter these by not emitting this signal for private errors since there is no way for the users of our API to check them (no enums...). They could be exposed but I believe it would just pollute our API as this sort of errors are more related to WebKit internals than to user's actions or decisions.
Created attachment 110890 [details] Patch
Comment on attachment 110890 [details] Patch Possible to test this?
(In reply to comment #2) > (From update of attachment 110890 [details]) > Possible to test this? I don't think so =/. Maybe only if the test rely on private stuff... but I'm not sure it makes sense. The good thing about this patch is that if anyone ever thinks these errors should emit loadFailed it's easy to remove those lines. Plus, other ports do the same on their FrameLoaderClient implementation in WebKit1 and we ourselves used to do the same in FrameLoaderClientQt::shouldFallBack. So I guess we are safe here... Can I land it, Kenneth?
Sure!
Comment on attachment 110890 [details] Patch Clearing flags on attachment: 110890 Committed r97398: <http://trac.webkit.org/changeset/97398>
All reviewed patches have been landed. Closing bug.