[Webkit-unassigned] [Bug 51823] New: <embed>, <object>, <iframe> don't use the parent QWebPage's networkAccessManager

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=51823

           Summary: <embed>, <object>, <iframe> don't use the parent
                    QWebPage's networkAccessManager
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebKit Qt
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: bero at arklinux.org


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" />

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.