Enable test that's no longer problematic
authorAryeh Gregor <ayg@aryeh.name>
Fri, 18 May 2012 06:13:37 -0600
changeset 730 727e691b1779
parent 729 c1369e156007
child 731 90017605b677
Enable test that's no longer problematic

Previously the spec required throwing for unrecognized commands, which
the data.js format didn't allow, so testing an unrecognized command
didn't work. Now it requires returning false/"", which the format does
support, so it can be re-enabled.
conformancetest/data.js
tests.js
--- a/conformancetest/data.js	Thu May 17 05:23:14 2012 -0600
+++ b/conformancetest/data.js	Fri May 18 06:13:37 2012 -0600
@@ -27649,6 +27649,11 @@
 	"foo[bar]baz",
 	[true],
 	{"usecss":[false,false,"",false,false,""]}],
+["foo[bar]baz",
+	[["quasit",""]],
+	"foo[bar]baz",
+	[false],
+	{"quasit":[false,false,"",false,false,""]}],
 ["foo[]bar",
 	[["bold",""],["inserttext","a"]],
 	"foo<b>a[]</b>bar",
--- a/tests.js	Thu May 17 05:23:14 2012 -0600
+++ b/tests.js	Fri May 18 06:13:37 2012 -0600
@@ -4079,7 +4079,7 @@
 		['falsé', 'foo[bar]baz'],
 	],
 	//@}
-	quasit: ['!foo[bar]baz'],
+	quasit: ['foo[bar]baz'],
 	multitest: [
 	//@{
 		// Insertion-affecting state.  Test that insertText works right, and