Bug 200298
| Summary: | [WPE][GTK] WebKitCookieManager fails to persist if its persistent storage set before WebKitWebsiteDataManager assigned to WebKitWebContext | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Andri Möll <andri> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | bugs-noreply, mcatanzaro |
| Priority: | P2 | ||
| Version: | Other | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Andri Möll
Hey,
Turns out if you get the cookie manager off of a new non-ephemeral WebKitWebsiteDataManager and set its persistence with `webkit_cookie_manager_set_persistent_storage`, that fails to take effect if you haven't created a WebKitWebContext with the data manager prior with `webkit_web_context_new_with_website_data_manager`. Because I think it's quite natural to configure a data manager before passing it onward for web context use, having such a "forward" dependency isn't intuitive. Nor mentioned in documentation, as far I noticed.
This with WebKitGTK v2.24.3.
Cheers
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Michael Catanzaro
Hm, I agree this is a problem. Basically all of the WebKitCookieManager functions will fail before the WebKitWebsiteDataManager is associated to a WebKitWebContext. That shouldn't be, but it's not straightforward to fix.
We used to have a similar bug, where the calls would fail even after the WebKitWebContext is associated if before the first web process is launched. (I'm pretty sure that's still broken on Mac, actually.)