+2006-01-30 Darin Adler <darin@apple.com>
+
+ Pointed out by Dave Kilzer.
+
+ - added test result I forgot to check in
+
+ * fast/dom/Range/range-exceptions-expected.txt: Added.
+
2006-01-30 Beth Dakin <bdakin@apple.com>
Layout test for <rdar://problem/4298052> Crash in
* fast/dom/Window/window-open-self-expected.txt: Added.
* fast/dom/Window/window-open-top-expected.txt: Added.
-2006-01-20 Darin Adler <darin@apple.com>
+2006-01-29 Darin Adler <darin@apple.com>
- added a test for the names of range exceptions, which were wrong
in my last commit until I made the fix Alexey suggested
--- /dev/null
+This test checks a few DOM range exceptions.
+
+On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
+
+
+PASS node.innerHTML is '<BAR>AB<MOO>C</MOO>DE</BAR>'
+PASS foo.outerHTML is '<FOO></FOO>'
+PASS range.surroundContents(foo) threw exception Error: BAD_BOUNDARYPOINTS_ERR: DOM Range Exception 1.
+PASS successfullyParsed is true
+
+TEST COMPLETE
+