[Webkit-unassigned] [Bug 84052] New: [EFL] FrameLoaderClient should send "load, finished" signal for all frame, not just the main one
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Apr 16 10:58:25 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=84052
Summary: [EFL] FrameLoaderClient should send "load,finished"
signal for all frame, not just the main one
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: WebKit EFL
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: christophe.dumez at intel.com
CC: demarchi at webkit.org, gyuyoung.kim at webkit.org
EFL's FrameLoaderClient currently emits the "load,finished" signal from the postProgressFinishedNotification() method. It apparently causes the signal to be emitted only for the main frame and not for other frame. It is more suited to emit the signal from dispatchDidFinishLoad() and dispatchDidFailLoad() so that we can send notification for all frames.
This change is needed to unskip several test cases which rely on the DumpRenderTree support for LayoutTestController's dumpFrameLoadCallbacks() and expect notifications for other frame than the main one:
* http/tests/security/mixedContent/empty-url-plugin-in-frame.html
* http/tests/security/mixedContent/about-blank-iframe-in-main-frame.html
* http/tests/security/mixedContent/data-url-iframe-in-main-frame.html
* http/tests/security/mixedContent/data-url-script-in-iframe.html
* http/tests/security/mixedContent/insecure-css-in-iframe.html
* http/tests/security/mixedContent/insecure-iframe-in-iframe.html
* http/tests/security/mixedContent/insecure-iframe-in-main-frame.html
* http/tests/security/mixedContent/insecure-image-in-iframe.html
* http/tests/security/mixedContent/redirect-http-to-https-script-in-iframe.html
* http/tests/security/mixedContent/redirect-https-to-http-script-in-iframe.html
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list