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

Unified Diff: third_party/WebKit/LayoutTests/fast/js/regexp-caching-expected.txt

Issue 1814963002: Use process/control messages (instead of RVH messages) for layout tests. Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Rebasing... Created 4 years, 3 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: third_party/WebKit/LayoutTests/fast/js/regexp-caching-expected.txt
diff --git a/third_party/WebKit/LayoutTests/fast/js/regexp-caching-expected.txt b/third_party/WebKit/LayoutTests/fast/js/regexp-caching-expected.txt
index 8513c8e2ce5da4baaa59b5e4194cbbb9e41c91b1..4ab36c18febe19a1285d4c0ebb9ac795f72e95e2 100644
--- a/third_party/WebKit/LayoutTests/fast/js/regexp-caching-expected.txt
+++ b/third_party/WebKit/LayoutTests/fast/js/regexp-caching-expected.txt
@@ -1,95 +1,23 @@
This test checks our implementation of the special RegExp member variables.
Properties of RegExp at startup:
-$1: {} (read-only)
-$2: {} (read-only)
-$3: {} (read-only)
-$4: {} (read-only)
-$5: {} (read-only)
-$6: {} (read-only)
-$7: {} (read-only)
-$8: {} (read-only)
-$9: {} (read-only)
-input: {} (read-write)
-lastMatch: {} (read-only)
-lastParen: {} (read-only)
-leftContext: {} (read-only)
-multiline: {false} (read-write)
-rightContext: {} (read-only)
Properties of RegExp after /(1)(2)(3)(4)(5)(6)(7)(8)(9)(0)/.exec(<1234567890>):
-$1: {1}
-$2: {2}
-$3: {3}
-$4: {4}
-$5: {5}
-$6: {6}
-$7: {7}
-$8: {8}
-$9: {9}
-input: {<1234567890>}
-lastMatch: {1234567890}
-lastParen: {0}
-leftContext: {<}
-multiline: {false}
-rightContext: {>}
RegExp.$0 does not exist
RegExp.$10 does not exist
RegExp doesn't use RegExp.input
-RegExp.multiline coerces values to booleans
+RegExp.multiline doesn't coerce values to booleans
RegExp.input coerces values to strings
Properties of RegExp after /(1)(2)(3)(4)(5)(6)(7)(8)(9)(0)/.exec(XXX):
-$1: {1}
-$2: {2}
-$3: {3}
-$4: {4}
-$5: {5}
-$6: {6}
-$7: {7}
-$8: {8}
-$9: {9}
-input: {0}
-lastMatch: {1234567890}
-lastParen: {0}
-leftContext: {<}
-multiline: {true}
-rightContext: {>}
+multiline: {foo}
---------- [Cleared RegExp values] ----------
Properties of RegExp after <1234567890>.search(/(1)(2)(3)(4)(5)(6)(7)(8)(9)(0)/):
-$1: {1}
-$2: {2}
-$3: {3}
-$4: {4}
-$5: {5}
-$6: {6}
-$7: {7}
-$8: {8}
-$9: {9}
-input: {<1234567890>}
-lastMatch: {1234567890}
-lastParen: {0}
-leftContext: {<}
-multiline: {true}
-rightContext: {>}
+multiline: {foo}
---------- [Cleared RegExp values] ----------
Properties of RegExp after <1234567890>.replace(/(1)(2)(3)(4)(5)(6)(7)(8)(9)(0)/):
-$1: {1}
-$2: {2}
-$3: {3}
-$4: {4}
-$5: {5}
-$6: {6}
-$7: {7}
-$8: {8}
-$9: {9}
-input: {<1234567890>}
-lastMatch: {1234567890}
-lastParen: {0}
-leftContext: {<}
-multiline: {true}
-rightContext: {>}
+multiline: {foo}

Powered by Google App Engine
This is Rietveld 408576698