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
| File | Mode | Size |
|---|---|---|
| resources | ||
| compile_worker.js | -rw-r--r-- | 294 bytes |
| create_multiple_memory.worker.js | -rw-r--r-- | 538 bytes |
| incrementer.wasm | -rw-r--r-- | 46 bytes |
| many-memories.window.js | -rw-r--r-- | 571 bytes |
| wasm_idb_worker.js | -rw-r--r-- | 790 bytes |
| wasm_indexeddb_test.https.html | -rw-r--r-- | 586 bytes |
| wasm_indexeddb_test.js | -rw-r--r-- | 3.5 KB |
| wasm_local_iframe_test.html | -rw-r--r-- | 734 bytes |
| wasm_serialization_tests.html | -rw-r--r-- | 309 bytes |
| wasm_serialization_tests.js | -rw-r--r-- | 590 bytes |
| wasm_serialization_worker.js | -rw-r--r-- | 580 bytes |
| wasm_service_worker_test.https.html | -rw-r--r-- | 1021 bytes |
Computing file changes ...
