144912 2015-05-12 07:30:45 -0700 WKWebView should expose _loadAlternateHTMLString:baseURL:forUnreachableURL: 2015-06-11 16:55:50 -0700 1 1 1 Unclassified WebKit WebKit2 528+ (Nightly build) Unspecified Unspecified NEW InRadar P2 Normal --- 1 stefan webkit-unassigned andersca ap benjamin sam webkit-bug-importer oldest_to_newest 1094156 0 stefan 2015-05-12 07:30:45 -0700 Exposing WKWebView#_loadAlternateHTMLString:baseURL:forUnreachableURL: would allow people to us show error messages in-content while maintaining a sane BackForwardList. The problem with the alternatives, loadHTML or loadRequest from an embedded HTTP Server, do not play well with the (read-only) BackForwardList. When presenting an error with loadHTML, it will *replace* the current page you are on. When presenting an error with loadRequest, either from embedded server or file: URL, it will generate a new entry in the BackForwardList that you cannot get rid of. The _loadAlternateHTMLString:baseURL:forUnreachableURL API seems to add the failing page to the BackForwardList while presenting alternative content, like an error message. This means a call to reloadFromOrigin will simply retry the page and leave the BackForwardList in a good state that makes sense. 1094324 1 stefan 2015-05-12 17:00:33 -0700 Would you accept a patch for exposing this functionality? I'm happy work with the WebKit team to produce something. 1101448 2 webkit-bug-importer 2015-06-11 16:55:50 -0700 <rdar://problem/21350071>