Updates:
Owner: ---
Comment #5 on issue 7386 by a...@chromium.org: GURL-related layout test
failure: http/security/postMessage/invalid-origin-throws-exception.html
http://code.google.com/p/chromium/issues/detail?id=7386
Adam, of course we are not rebaselining tests without
Comment #6 on issue 7386 by aba...@chromium.org: GURL-related layout test
failure: http/security/postMessage/invalid-origin-throws-exception.html
http://code.google.com/p/chromium/issues/detail?id=7386
ager: When we find that a test is wrong according to the spec, do we file
bugs
upstream?
Comment #3 on issue 7386 by bre...@chromium.org: GURL-related layout test
failure: http/security/postMessage/invalid-origin-throws-exception.html
http://code.google.com/p/chromium/issues/detail?id=7386
Adam: I looked briefly at this test but I don't know anything about
postMessage. Can
you
Comment #4 on issue 7386 by aba...@chromium.org: GURL-related layout test
failure: http/security/postMessage/invalid-origin-throws-exception.html
http://code.google.com/p/chromium/issues/detail?id=7386
From the test results, it looks like http: is failing to parse as a URL
and throwing a
Status: Untriaged
Owner: a...@chromium.org
CC: bre...@chromium.org
Labels: Type-Bug Pri-2 OS-All Area-WebKit
New issue 7386 by a...@chromium.org: GURL-related layout test failure:
http/security/postMessage/invalid-origin-throws-exception.html
Updates:
Status: Assigned
Comment #1 on issue 7386 by bre...@chromium.org: GURL-related layout test
failure: http/security/postMessage/invalid-origin-throws-exception.html
http://code.google.com/p/chromium/issues/detail?id=7386
(No comment was entered for this change.)
--
You
Updates:
Cc: aba...@chromium.org
Comment #2 on issue 7386 by aba...@chromium.org: GURL-related layout test
failure: http/security/postMessage/invalid-origin-throws-exception.html
http://code.google.com/p/chromium/issues/detail?id=7386
I wrote this test, and I think the spec requires
