Bug 116537
| Summary: | can no longer veto the showing of WebKitGTK's default authentication prompter | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Grant Gayed <grant_gayed> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | brian.holt, kapouer, mrobinson, spena |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 99352 | ||
| Bug Blocks: | |||
Grant Gayed
- 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
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
Making it depend on bug #99352 on behalf of Brian.
Grant Gayed
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
(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.