Bug 105899 – Pass through SynchronousRequestAttribute to QNetworkReplyHandler::start

• Status: RESOLVED
• Resolution: INVALID
• Component: WebKit Qt

[Azat Khuzhin]

If you try to set "SynchronousRequestAttribute" from "QNetworkAccessManager::createRequest"
<pre>
    QNetworkRequest nonConstRequest(request);
    nonConstRequest.setAttribute(QNetworkRequest::SynchronousRequestAttribute, true);
    QNetworkReply *reply = QNetworkAccessManager::createRequest(operation, nonConstRequest, outgoingData);
    return reply;
</pre>
Qt webkit browser didn't render page, because it just load one resource, and all pending not.

In my opinion because after "QNetworkAccessManager::createRequest" request already finished, and when webkit attach to finished() signal non of event will be triggered.

After some investigations, I'v write a little patch (attached).
This must fix issue.

[Azat Khuzhin]

Created attachment 180996 [details]
Pass through SynchronousRequestAttribute to QNetworkReplyHandler::start

[Early Warning System Bot]

Comment on attachment 180996 [details]
Pass through SynchronousRequestAttribute to QNetworkReplyHandler::start

Attachment 180996 [details] did not pass qt-ews (qt):
Output: http://queues.webkit.org/results/15762135

[Early Warning System Bot]

Comment on attachment 180996 [details]
Pass through SynchronousRequestAttribute to QNetworkReplyHandler::start

Attachment 180996 [details] did not pass qt-wk2-ews (qt):
Output: http://queues.webkit.org/results/15771086

[Azat Khuzhin]

Created attachment 181757 [details]
002-Pass through SynchronousRequestAttribute to QNetworkReplyHandler::start

[Azat Khuzhin]

New fixed patch attached

First one was totally wrong, because I looked at the wrong place of diff.

[Azat Khuzhin]

Any news?

[Alexey Proskuryakov]

The Qt port has been removed from WebKit, resolving this bug.