Bug 51823 – [Qt] <embed>, <object>, <iframe> don't use the parent QWebPage's networkAccessManager

• Status: RESOLVED
• Resolution: INVALID
• Component: Page Loading

[Bernhard Rosenkraenzer]

When using a custom QNetworkAccessManager (extended to handle new protocols), images (<img src="..."/>) and links (<a href="...">) are loaded correctly even if they use the new protocol.
<embed>, <object> and <iframe>, however, don't use the right QNetworkAccessManager, causing their content not to be loaded.

e.g. with
<base href="myProtocol://xyz/"/>

this works:

<img src="test.svg"/><!-- rendered with QtSvg as opposed to WebKit SVG -->
<div><a href="page2.html">Go to the next page</a></div>

but this does not:

<embed src="test.svg" type="image/svg+xml"/>
<object data="test.svg" type="image/svg+xml"/>
<iframe src="test.svg" />

[Benjamin Poulain]

Could you attach a test case?

This is really strange because we don't have any "backup solution". To load something, we have to go through the network access manager.

[Jocelyn Turcotte]

=== 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.