Bug 95935 - [Qt][WK2] New http/tests/security/cross-origin-plugin* tests fail
Summary: [Qt][WK2] New http/tests/security/cross-origin-plugin* tests fail
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: Qt, QtTriaged
Depends on:
Blocks: 87008 94888
  Show dependency treegraph
 
Reported: 2012-09-05 22:48 PDT by Csaba Osztrogonác
Modified: 2014-02-03 03:22 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Csaba Osztrogonác 2012-09-05 22:48:03 PDT
New http/tests/security/cross-origin-plugin* tests introduced in 
https://trac.webkit.org/changeset/127513 fail on Qt WK2.

Could you check it, please?

--- /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/security/cross-origin-plugin-allowed-expected.txt
+++ /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/security/cross-origin-plugin-allowed-actual.txt
@@ -8,9 +8,9 @@
 --------
 Frame: '<!--framePath //<!--frame0-->-->'
 --------
-false
+undefined
 
 --------
 Frame: '<!--framePath //<!--frame1-->-->'
 --------
-false
+undefined



--- /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/security/cross-origin-plugin-private-browsing-toggled-allowed-expected.txt
+++ /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/security/cross-origin-plugin-private-browsing-toggled-allowed-actual.txt
@@ -8,9 +8,9 @@
 --------
 Frame: '<!--framePath //<!--frame0-->-->'
 --------
-false
+undefined
 
 --------
 Frame: '<!--framePath //<!--frame1-->-->'
 --------
-false
+undefined



--- /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/security/cross-origin-plugin-private-browsing-toggled-expected.txt
+++ /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/security/cross-origin-plugin-private-browsing-toggled-actual.txt
@@ -8,9 +8,9 @@
 --------
 Frame: '<!--framePath //<!--frame0-->-->'
 --------
-false
+undefined
 
 --------
 Frame: '<!--framePath //<!--frame1-->-->'
 --------
-false
+undefined



--- /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/security/cross-origin-plugin-expected.txt
+++ /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/security/cross-origin-plugin-actual.txt
@@ -8,9 +8,9 @@
 --------
 Frame: '<!--framePath //<!--frame0-->-->'
 --------
-false
+undefined
 
 --------
 Frame: '<!--framePath //<!--frame1-->-->'
 --------
-false
+undefined
Comment 1 Csaba Osztrogonác 2012-09-05 23:07:11 PDT
I skipped them to paint the bot green - https://trac.webkit.org/changeset/127697
Please unskip it with the proper fix.
Comment 2 Vicki Pfau 2012-09-06 17:37:23 PDT
It looks like what's going wrong here might be that the plugin element isn't getting its .privateBrowsingEnabled member set at all, although I don't really know why this might be the case. It's likely some interaction with the testing tools failing.
Comment 3 Vicki Pfau 2012-09-14 14:32:28 PDT
Fair warning, the patch to https://bugs.webkit.org/show_bug.cgi?id=95790 will likely cause similar failures for storage-blocking-*-plugin-* tests.
Comment 4 Jocelyn Turcotte 2014-02-03 03:22:27 PST
=== 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.