28195 2015-03-11 19:55:51 +0000 It is not specified what error should be raised by findElement(s) operation if an invalid XPath/CSS query passed in 2016-05-09 10:03:15 +0000 1 1 1 Unclassified Browser Test/Tools WG WebDriver unspecified PC Windows NT RESOLVED FIXED P2 normal --- 20860 1 barancev public-browser-tools-testing dburns mike simon.m.stewart public-browser-tools-testing oldest_to_newest 118531 0 barancev 2015-03-11 19:55:51 +0000 It is not specified what error should be raised by findElement(s) operation if an invalid XPath/CSS query passed in 123935 1 simon.m.stewart 2015-10-26 05:29:56 +0000 We should bubble the syntax error back to the user if the underlying mechanism supports it. 126383 2 dburns 2016-05-09 10:03:15 +0000 This was fixed in https://github.com/w3c/webdriver/commit/9cf22343620b78ad18b46f99ae542fe49112727b and https://github.com/w3c/webdriver/commit/377d896a3380a05b9eb31900b16d60fbcd8fdf28