Bug 44365
Summary: | [Qt] http/tests/security/mixedContent/insecure-css-in-main-frame.html fails when run alone | ||
---|---|---|---|
Product: | WebKit | Reporter: | Ademar Reis <ademar> |
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | abarth, ossy, sam |
Priority: | P2 | Keywords: | Qt, QtTriaged |
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | Linux |
Ademar Reis
$ run-webkit-tests http/tests/security/mixedContent/insecure-css-in-main-frame.html --> FAILS
$ run-webkit-tests http/tests/security/mixedContent/ --> All tests pass
DRT sideeffect somewhere. I remember seeing this particular test failing once in the build bot for unknown reasons, so it may be flaky
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Csaba Osztrogonác
I can reproduce this bug with r65806 (ToT).
I cc-ed Adam and Sam, the author and the reviewer of this test.
https://bugs.webkit.org/show_bug.cgi?id=29003
Have you got any idea what's wrong with Qt-DRT?
diff:
-- /tmp/layout-test-results/http/tests/security/mixedContent/insecure-css-in-main-frame-expected.txt 2010-08-23 07:36:02.581087147 -0700
+++ /tmp/layout-test-results/http/tests/security/mixedContent/insecure-css-in-main-frame-actual.txt 2010-08-23 07:36:02.581087147 -0700
@@ -5,6 +5,4 @@
main frame - didCommitLoadForFrame
didDisplayInsecureContent
main frame - didFinishDocumentLoadForFrame
-main frame - didHandleOnloadEventsForFrame
-main frame - didFinishLoadForFrame
This test opens a window that loads an insecure style sheet. We should trigger a mixed content callback because the main frame in the window is HTTPS but is displaying insecure content.
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.