[Webkit-unassigned] [Bug 69255] [GTK] Implement default error pages in WebKit2 GTK+ API

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Oct 3 09:54:27 PDT 2011


Martin Robinson <mrobinson at webkit.org> changed:

           What    |Removed                     |Added
                 CC|                            |mrobinson at webkit.org

--- Comment #4 from Martin Robinson <mrobinson at webkit.org>  2011-10-03 09:54:27 PST ---
(In reply to comment #3)
> (In reply to comment #2)
> > (From update of attachment 109475 [details] [details])
> > View in context: https://bugs.webkit.org/attachment.cgi?id=109475&action=review
> > 
> > Looks fine to me, but I'm not sure if it's the right thing to do to "hide" the loading of the error page from the API.
> > 
> It's not hidden, provisional-load-failed and load-failed signals documentation say that a custom error page will be loaded if the user doesn't handle the signal. The behaviour is exactly the same than webkit1 API.

I was referring to the loading of the custom error page. I was referring to the fact that you cannot observe the loading signals as the custom error page loads. Note that this does not happen on the Mac port. I think we should follow the approach of firing the signals. At least the conservative decision is to fire them now and let the UA track if it is loading an error page.

I'm guessing the original decision was made to not break Epiphany. Since we are rewriting this code in Epiphany anyway, we can make whatever decision we want. My tendency is to be more similar to other ports.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list