Summary: | [Qt] cleaning up QNetworkReply | ||
---|---|---|---|
Product: | WebKit | Reporter: | Johannes Zellner <johannes.zellner> |
Component: | WebKit Qt | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | adjam7, benjamin, markus, pd |
Priority: | P3 | Keywords: | EasyFix, Qt, QtTriaged |
Version: | 418.x | ||
Hardware: | PC | ||
OS: | Linux |
Description
Johannes Zellner
2010-04-20 06:59:26 PDT
Can you please provide a simple test case for this? There's no QWebPage::finished(QNetworkReply*) [signal] present in the API. There are void QWebPage::loadFinished ( bool ok ) [signal] and void QNetworkAccessManager::finished ( QNetworkReply * reply ) [signal] Did you mean the second one? sorry you are right, I meant the void QNetworkAccessManager::finished ( QNetworkReply * reply ) [signal] === Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines. |