Commit 091ae8ce authored by abarth@webkit.org's avatar abarth@webkit.org

2010-12-31 Adam Barth <abarth@webkit.org>

        Remove custom Chromium expectation for invalid-protocol.  Now that we
        share more code with JavaScriptCore, we throw exactly the same
        exception and therefore can share results.

        * platform/chromium/fast/dom/Window/invalid-protocol-expected.txt: Removed.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@74835 268f45cc-cd09-0410-ab3c-d52691b4dbfc
parent fa77fc94
2010-12-31 Adam Barth <abarth@webkit.org>
Remove custom Chromium expectation for invalid-protocol. Now that we
share more code with JavaScriptCore, we throw exactly the same
exception and therefore can share results.
* platform/chromium/fast/dom/Window/invalid-protocol-expected.txt: Removed.
2010-12-29 Zhenyao Mo <zmo@google.com>
Reviewed by Kenneth Russell.
......
Test URL protocol setter.
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
PASS location.protocol = '' threw exception SyntaxError: Can't set protocol.
PASS location.protocol = ':' threw exception SyntaxError: Can't set protocol.
PASS location.protocol = 'é' threw exception SyntaxError: Can't set protocol.
PASS location.protocol = '[' threw exception SyntaxError: Can't set protocol.
PASS location.protocol = '0' threw exception SyntaxError: Can't set protocol.
PASS a.protocol is 'http:'
PASS a.href is 'https://www.apple.com/'
PASS a.href is 'http://www.apple.com/'
PASS a.href is 'https://www.apple.com/'
PASS successfullyParsed is true
TEST COMPLETE
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment