Remove XPathException

LayoutTests/dom/svg/level3/xpath/XPathEvaluator_createExpression_INVALID_EXPRESSION_ERR.js

Index: LayoutTests/dom/svg/level3/xpath/XPathEvaluator_createExpression_INVALID_EXPRESSION_ERR.js
diff --git a/LayoutTests/dom/svg/level3/xpath/XPathEvaluator_createExpression_INVALID_EXPRESSION_ERR.js b/LayoutTests/dom/svg/level3/xpath/XPathEvaluator_createExpression_INVALID_EXPRESSION_ERR.js
index 67a32362fa5ca2eb503a0b9c1817b6770770524b..3ad53b25a9f93cbaa8319b15a5448e93789fd86c 100644
--- a/LayoutTests/dom/svg/level3/xpath/XPathEvaluator_createExpression_INVALID_EXPRESSION_ERR.js
+++ b/LayoutTests/dom/svg/level3/xpath/XPathEvaluator_createExpression_INVALID_EXPRESSION_ERR.js
@@ -79,7 +79,7 @@ function loadComplete() {
       'createExpression("12a", null)' method is
       invoked with the document element.  The method should fail to create
       pre-compiled expression and throws
-      XPathException.INVALID_EXPRESSION_ERR
+      SYNTAX_ERR
       since "12a" is not an XPath expression.
     
 * @author Philippe Le Hégaret
@@ -107,7 +107,7 @@ function XPathEvaluator_createExpression_INVALID_EXPRESSION_ERR() {
             exp = xpEvaluator.createExpression("12a",nullNSResolver);
         }
 		catch(ex) {            
-      success = (typeof(ex.code) != 'undefined' && ex.code == 51);
+      success = ex.name == 'SyntaxError';

[abarth-chromium, 2013/06/18 19:30:33]

This looks like a W3C test.  Maybe we should update our expected.txt files
rather than changing the test?

[arv (Not doing code reviews), 2013/06/18 19:34:30]

I'm fine either way. Changing the expectation means we lose test coverage
because they will just say fail. The output is not good enough to test the
correct behavior.

 		}
 		assertTrue("throw_INVALID_EXPRESSION_ERR",success);
 	}