Details
-
Suggestion
-
Resolution: Fixed
-
P2: Important
-
None
-
None
-
889567af4 (112-based), 37430020d (dev)
Description
With this change
https://github.com/qt/qtwebengine/commit/75412200db05ddc5ee2b9aea367b580d8b0c438e#diff-82fae0ea12cd786b0b9aa0c5e4c50de33d87b0bcc4ccb89176c8dbea8acaf769R671
calls to clearHttpCache do not immediatly reset the network context, and only do so after a call to BrowsingDataRemoverObserverQt::OnBrowsingDataRemoverDone() I would very much like it if that was either a signal I could connect to or if the result of clearHttpCache was a form of promise that I could await for further processing.
Attachments
Issue Links
- relates to
-
QTBUG-111541 QWebEngineProfile::clearHttpCache() can subsequently cause QWebEnginePage::load() to hang
-
- Closed
-
| For Gerrit Dashboard: QTBUG-89670 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 492736,6 | Add clearHttpCacheCompleted signal to profile | dev | qt/qtwebengine | Status: MERGED | +2 | 0 |
| 493884,3 | Make NetworkContext resettable | 112-based | qt/qtwebengine-chromium | Status: MERGED | +2 | 0 |