Currently we always fail with stale element error when we fail to find a node. There are two options in the spec: get a known element and get a known connected element: To get a known element with argument reference, run the following steps: 1. Let element be the item in the current browsing context's list of known elements for which the web element reference matches reference, if such an element exists. Otherwise return error with error code no such element. 2. If element is stale, return error with error code stale element reference. Return success with element. To get a known connected element with argument reference, run the following steps: 1. Let element be the result of trying to get a known element with argument reference. 2. If element is not connected return error with error code stale element reference. 3. Return success with element. This is causing several tests to fail: imported/w3c/webdriver/tests/state/get_element_property.py::test_element_not_found imported/w3c/webdriver/tests/state/get_element_attribute.py::test_element_not_found imported/w3c/webdriver/tests/state/get_element_tag_name.py::test_element_not_found with similat backtrace in all the cases: response = <Response status=404 error=<StaleElementReferenceException http_status=404>>, error_code = 'no such element' def assert_error(response, error_code): """ Verify that the provided webdriver.Response instance described a valid error response as defined by `dfn-send-an-error` and the provided error code. :param response: ``webdriver.Response`` instance. :param error_code: String value of the expected error code """ assert response.status == errors[error_code] assert "value" in response.body > assert response.body["value"]["error"] == error_code E AssertionError error_code = 'no such element' response = <Response status=404 error=<StaleElementReferenceException http_status=404>>
*** This bug has been marked as a duplicate of bug 204684 ***