Revision 89ba9443f1d80b2bea3a33477b1ac53585fbb16d authored by jimevans on 16 March 2018, 14:46:32 UTC, committed by Andreas Tolfsen on 16 March 2018, 14:46:32 UTC
When the context element is `document.documentElement`, and an attempt is made to find elements from that context element using an XPath of `..`, a snapshot is returned containing the `document` object. While this is apparently the correct behavior for XPath, the WebDriver spec says that if the object in the snapshot is not an element, we should return an error with error code "invalid selector." The test_parent_htmldocument test in both find_element_from_element.py and find_elements_from_element.py expect a success in this case. This commit changes the tests to correctly expect an error from the driver.
1 parent 1cbb928
WorkerGlobalScope_setTimeout.htm
<!DOCTYPE html>
<title> WorkerGlobalScope API: setTimeout() </title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<div id=log></div>
<script>
async_test(function(t) {
var result = [];
var worker = new Worker('./support/Timer.js');
worker.onmessage = t.step_func(function(e) {
result.push(e.data);
if (result.length == 3) {
assert_array_equals(result, ["hello", "worker", "worker"]);
worker.onmessage = t.unreached_func('Unexpected message event');
setTimeout(t.step_func_done(), 100);
}
});
worker.postMessage("TimeoutHandler");
});
</script>
Computing file changes ...
