116537 2013-05-21 07:45:29 -0700 can no longer veto the showing of WebKitGTK's default authentication prompter 2013-08-09 06:28:40 -0700 1 1 1 Unclassified WebKit WebKitGTK 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX P2 Normal --- 99352 0 grant_gayed webkit-unassigned brian.holt kapouer mrobinson spena oldest_to_newest 891763 0 grant_gayed 2013-05-21 07:45:29 -0700 - using WebKit1 API Prior to WebKitGTK 2.0 we could replace the default WebKitGTK soup authentication prompter by connecting our "authenticate" signal handler before it (so that we would be invoked first), and then stopping the emission of the signal in our handler (so that the default prompter would not subsequently be shown). However as of 2.0.x, WebKitGTK's default authentication prompter is always shown after ours, even if our prompter has already performed the authentication (ie.- stopping the emission of the "authenticate" signal is no longer effective). 911020 1 brian.holt 2013-07-23 06:35:47 -0700 This is being fixed in https://bugs.webkit.org/show_bug.cgi?id=99352 (can't make it depend - don't have editbug privileges). 911036 2 spena 2013-07-23 07:43:30 -0700 Making it depend on bug #99352 on behalf of Brian. 915229 3 grant_gayed 2013-08-07 11:33:21 -0700 It's good to see that a formal API is being introduced to handle this in bug 99352. However I'm guessing that this API would not be added to the WebKit1 stream since it's now API-frozen? 915783 4 brian.holt 2013-08-09 05:56:54 -0700 (In reply to comment #3) > It's good to see that a formal API is being introduced to handle this in bug 99352. However I'm guessing that this API would not be added to the WebKit1 stream since it's now API-frozen? No, WebKit1 is now in maintenance mode so no new APIs are being added.