summaryrefslogtreecommitdiffstats
path: root/webkit
diff options
context:
space:
mode:
authoratwilson@chromium.org <atwilson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-09-23 15:42:25 +0000
committeratwilson@chromium.org <atwilson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-09-23 15:42:25 +0000
commit2b23e70897db3644a1f2ce08a094eebfa0214914 (patch)
treea22f1dc435ec4a12cddb19c004a4b657124c9c61 /webkit
parent9c5eeaca38c8ff13fad449bb9d9a3263aba73c8d (diff)
downloadchromium_src-2b23e70897db3644a1f2ce08a094eebfa0214914.zip
chromium_src-2b23e70897db3644a1f2ce08a094eebfa0214914.tar.gz
chromium_src-2b23e70897db3644a1f2ce08a094eebfa0214914.tar.bz2
Reverting 26919.
Review URL: http://codereview.chromium.org/224003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26926 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit')
-rw-r--r--webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/events/message-port-multi-expected.txt18
-rw-r--r--webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/workers/worker-context-multi-port-expected.txt16
-rw-r--r--webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/workers/worker-multi-port-expected.txt16
3 files changed, 0 insertions, 50 deletions
diff --git a/webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/events/message-port-multi-expected.txt b/webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/events/message-port-multi-expected.txt
deleted file mode 100644
index 981eb92f..0000000
--- a/webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/events/message-port-multi-expected.txt
+++ /dev/null
@@ -1,18 +0,0 @@
-This test checks the various use cases around sending multiple ports through MessagePort.postMessage
-
-On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
-
-
-PASS channel.port1.postMessage("same port", [channel.port1]) threw exception Error: INVALID_STATE_ERR: DOM Exception 11.
-PASS channel.port1.postMessage("entangled port", [channel.port2]) threw exception Error: INVALID_STATE_ERR: DOM Exception 11.
-PASS channel.port1.postMessage("null port", [channel3.port1, null, channel3.port2]) threw exception Error: INVALID_STATE_ERR: DOM Exception 11.
-PASS channel.port1.postMessage("notAPort", [channel3.port1, {}, channel3.port2]) threw exception TypeError: MessagePortArray argument must contain only MessagePorts.
-PASS channel.port1.postMessage("notAnArray", channel3.port1) threw exception TypeError: MessagePortArray argument has no length attribute.
-PASS channel.port1.postMessage("notASequence", [{length: 3}]) threw exception TypeError: MessagePortArray argument must contain only MessagePorts.
-PASS event.ports is null when no port sent
-PASS event.ports is null when empty array sent
-PASS event.ports contains two ports when two ports sent
-PASS event.ports contains two ports when two ports re-sent after error
-
-TEST COMPLETE
-
diff --git a/webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/workers/worker-context-multi-port-expected.txt b/webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/workers/worker-context-multi-port-expected.txt
deleted file mode 100644
index e66270f..0000000
--- a/webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/workers/worker-context-multi-port-expected.txt
+++ /dev/null
@@ -1,16 +0,0 @@
-This test checks the various use cases around sending multiple ports through WorkerGlobalScope.postMessage
-
-On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
-
-
-PASS event.ports is null when no port sent
-PASS event.ports is null when empty array sent
-PASS event.ports contains two ports when two ports sent
-PASS posting a null port did throw: Error: INVALID_STATE_ERR: DOM Exception 11
-PASS posting a non-port did throw: TypeError: MessagePortArray argument must contain only MessagePorts
-PASS event.ports contains two ports when two ports re-sent after error
-PASS posting a non-array did throw: TypeError: MessagePortArray argument has no length attribute
-PASS posting a non-sequence did throw: TypeError: MessagePortArray argument must contain only MessagePorts
-
-TEST COMPLETE
-
diff --git a/webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/workers/worker-multi-port-expected.txt b/webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/workers/worker-multi-port-expected.txt
deleted file mode 100644
index f11c74c..0000000
--- a/webkit/data/layout_tests/platform/chromium-win/LayoutTests/fast/workers/worker-multi-port-expected.txt
+++ /dev/null
@@ -1,16 +0,0 @@
-This test checks the various use cases around sending multiple ports through Worker.postMessage
-
-On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
-
-
-PASS worker.postMessage("null port", [channel3.port1, null, channel3.port2]) threw exception Error: INVALID_STATE_ERR: DOM Exception 11.
-PASS worker.postMessage("notAPort", [channel3.port1, {}, channel3.port2]) threw exception TypeError: MessagePortArray argument must contain only MessagePorts.
-PASS worker.postMessage("notAnArray", channel3.port1) threw exception TypeError: MessagePortArray argument has no length attribute.
-PASS worker.postMessage("notASequence", [{length: 3}]) threw exception TypeError: MessagePortArray argument must contain only MessagePorts.
-PASS event.ports is null when no port sent
-PASS event.ports is null when empty array sent
-PASS event.ports contains two ports when two ports sent
-PASS event.ports contains two ports when two ports re-sent after error
-
-TEST COMPLETE
-