RESOLVED WONTFIX 116537
can no longer veto the showing of WebKitGTK's default authentication prompter 
https://bugs.webkit.org/show_bug.cgi?id=116537
Summary can no longer veto the showing of WebKitGTK's default authentication prompter
Grant Gayed
Reported 2013-05-21 07:45:29 PDT
- 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).
Attachments
Add attachment proposed patch, testcase, etc.
Brian Holt
Comment 1 2013-07-23 06:35:47 PDT
This is being fixed in https://bugs.webkit.org/show_bug.cgi?id=99352 (can't make it depend - don't have editbug privileges).
Simon Pena
Comment 2 2013-07-23 07:43:30 PDT
Making it depend on bug #99352 on behalf of Brian.
Grant Gayed
Comment 3 2013-08-07 11:33:21 PDT
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?
Brian Holt
Comment 4 2013-08-09 05:56:54 PDT
(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.
Note You need to log in before you can comment on or make changes to this bug.