[Webkit-unassigned] [Bug 34702] [Qt] Make possible Qt DRT dump frame load callbacks
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Feb 10 13:07:00 PST 2010
https://bugs.webkit.org/show_bug.cgi?id=34702
--- Comment #4 from Diego Gonzalez <diego.gonzalez at openbossa.org> 2010-02-10 13:06:59 PST ---
The fallowing tests are still failing:
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/insecure-css-in-main-frame.html
http/tests/security/mixedContent/insecure-iframe-in-main-frame.html
http/tests/security/mixedContent/insecure-image-in-main-frame.html
http/tests/security/mixedContent/redirect-http-to-https-iframe-in-main-frame.html
http/tests/security/mixedContent/redirect-https-to-http-iframe-in-main-frame.html
Needs to evaluate the expected files are correct for Qt or there
is a sync problem to get the results as expected. There is a pattern in the
results
of failed tests.
the tests:
http/tests/security/mixedContent/insecure-css-in-main-frame.html
http/tests/security/mixedContent/insecure-iframe-in-main-frame.html
have the added two more lines as expected:
+main frame - didFailProvisionalLoadWithError
+main frame - didStartProvisionalLoadForFrame
the tests:
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/insecure-image-in-main-frame.html
http/tests/security/mixedContent/redirect-http-to-https-iframe-in-main-frame.html
http/tests/security/mixedContent/redirect-https-to-http-iframe-in-main-frame.html
also have the lines:
+main frame - didFailProvisionalLoadWithError
+main frame - didStartProvisionalLoadForFrame
but is missing the:
-main frame - didFinishLoadForFrame
The Qt FrameLoaderClient should be investigated more to get results difference
reason.
--
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