Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(80)

Unified Diff: LayoutTests/fast/dom/Range/surroundContents-crash-expected.txt

Issue 178543013: Fix a bug in Range::didSplitTextNode() that may yield an invalid Range object. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Fix comments in test. Created 6 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: LayoutTests/fast/dom/Range/surroundContents-crash-expected.txt
diff --git a/LayoutTests/fast/dom/Range/surroundContents-crash-expected.txt b/LayoutTests/fast/dom/Range/surroundContents-crash-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..ecbafd26610841bc3571493914523dfeacf91c56
--- /dev/null
+++ b/LayoutTests/fast/dom/Range/surroundContents-crash-expected.txt
@@ -0,0 +1,20 @@
+Range::didSplitTextNode() should not yield an invalid Range object nor cause a crash inside surroundContents().
+
+On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
+
+
+PASS textContainer.childNodes.length is 1
+PASS range.startContainer === textToBeSplit is true
+PASS range.startOffset is 7
+PASS range.endContainer === textContainer is true
+PASS range.endOffset is 1
+PASS textContainer.childNodes.length is 3
+PASS range.startContainer === newTextNode is true
+PASS range.startOffset is 1
+PASS range.endContainer === textContainer is true
+PASS range.endOffset is 3
+PASS Did not crash.
+PASS successfullyParsed is true
+
+TEST COMPLETE
+

Powered by Google App Engine
This is Rietveld 408576698