MORPH
SIGN IN SIGN UP
SeleniumHQ / selenium UNCLAIMED

A browser automation framework and ecosystem.

34196 0 51 Java
Normal View History Raw
Copyright uniformity for C++ projects Fixes copyright notices for files in the iedriver, iedriverserver, and webdriver-server, in accordance with issue #401.
2015-04-13 12:09:26 -04:00
// Licensed to the Software Freedom Conservancy (SFC) under one
// or more contributor license agreements. See the NOTICE file
// distributed with this work for additional information
// regarding copyright ownership. The SFC licenses this file
// to you under the Apache License, Version 2.0 (the "License");
KristianRosenvold: Removed windows carriage returns
2013-01-11 22:18:32 +01:00
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
#include "response.h"
Integrating the Microsoft Internet Explorer driver implementation This commit optionally allows the user to use the Microsoft-supplied implementation of WebDriver for IE 11 and above. To use the Microsoft implementation, the user must have the August 2014 updates to Internet Explorer installed through Windows Update, and must install the IE Web Driver Tool for Internet Explorer 11 download from Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=44069). Once those prerequisites are installed, the user can use the InternetExplorerDriverService object in the language bindings to set the implementation to be used. By default, the driver will continue to use the driver implementation developed by the open-source project. Over time as the Microsoft implementation matures, this will be switched to use that implementation, first by default, then exclusively.
2014-09-05 02:00:00 +00:00
#include "errorcodes.h"
KristianRosenvold: Removed windows carriage returns
2013-01-11 22:18:32 +01:00
#include "logging.h"
namespace webdriver {
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
Response::Response(void) : error_(""), value_(Json::Value::null), additional_data_(Json::Value::null) {
KristianRosenvold: Removed windows carriage returns
2013-01-11 22:18:32 +01:00
}
Response::~Response(void) {
}
void Response::Deserialize(const std::string& json) {
LOG(TRACE) << "Entering Response::Deserialize";
Json::Value response_object;
Updating JsonCpp library to latest This is to resolve issues with creating a JSON value that contains the empty string. Fixes issue #5664.
2018-03-22 13:55:29 -07:00
std::string parse_errors;
std::stringstream json_stream;
json_stream.str(json);
Json::parseFromStream(Json::CharReaderBuilder(),
json_stream,
&response_object,
&parse_errors);
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
Json::Value value_object;
if (response_object.isMember("value")) {
value_object = response_object["value"];
if (value_object.isObject() && value_object.isMember("error")) {
this->error_ = value_object["error"].asString();
this->value_ = value_object["message"].asString();
Fixing incorrect error response format for invalid commands in IE Previously, when an invalid command was sent to the IE driver, the response was not completely valid for the W3C dialect of the wire protocol. In particular, the distinction was lost between an unknown URL and an invalid HTTP verb, and this code was not properly converted when the driver was updated to implement the specification. This change fixes that. Correct responses are now sent back for both invalid command cases. Additionally, the driver no longer hand-codes JSON for these responses, instead creating a valid Response object, and using the common serialization mechanism for transmission. Finally, this commit includes some minor code formatting cleanup, which does not affect the functionality of the driver. Fixes issue #6828.
2019-01-10 17:20:12 -08:00
if (value_object.isMember("data")) {
this->additional_data_ = value_object["data"];
}
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
} else {
this->error_ = "";
this->value_ = value_object;
}
Integrating the Microsoft Internet Explorer driver implementation This commit optionally allows the user to use the Microsoft-supplied implementation of WebDriver for IE 11 and above. To use the Microsoft implementation, the user must have the August 2014 updates to Internet Explorer installed through Windows Update, and must install the IE Web Driver Tool for Internet Explorer 11 download from Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=44069). Once those prerequisites are installed, the user can use the InternetExplorerDriverService object in the language bindings to set the implementation to be used. By default, the driver will continue to use the driver implementation developed by the open-source project. Over time as the Microsoft implementation matures, this will be switched to use that implementation, first by default, then exclusively.
2014-09-05 02:00:00 +00:00
} else {
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
this->value_ = Json::Value::null;
Integrating the Microsoft Internet Explorer driver implementation This commit optionally allows the user to use the Microsoft-supplied implementation of WebDriver for IE 11 and above. To use the Microsoft implementation, the user must have the August 2014 updates to Internet Explorer installed through Windows Update, and must install the IE Web Driver Tool for Internet Explorer 11 download from Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=44069). Once those prerequisites are installed, the user can use the InternetExplorerDriverService object in the language bindings to set the implementation to be used. By default, the driver will continue to use the driver implementation developed by the open-source project. Over time as the Microsoft implementation matures, this will be switched to use that implementation, first by default, then exclusively.
2014-09-05 02:00:00 +00:00
}
KristianRosenvold: Removed windows carriage returns
2013-01-11 22:18:32 +01:00
}
std::string Response::Serialize(void) {
LOG(TRACE) << "Entering Response::Serialize";
Json::Value json_object;
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
if (this->error_.size() > 0) {
Json::Value error_object;
error_object["error"] = this->error_;
error_object["message"] = this->value_.asString();
error_object["stacktrace"] = "";
Fixing incorrect error response format for invalid commands in IE Previously, when an invalid command was sent to the IE driver, the response was not completely valid for the W3C dialect of the wire protocol. In particular, the distinction was lost between an unknown URL and an invalid HTTP verb, and this code was not properly converted when the driver was updated to implement the specification. This change fixes that. Correct responses are now sent back for both invalid command cases. Additionally, the driver no longer hand-codes JSON for these responses, instead creating a valid Response object, and using the common serialization mechanism for transmission. Finally, this commit includes some minor code formatting cleanup, which does not affect the functionality of the driver. Fixes issue #6828.
2019-01-10 17:20:12 -08:00
if (!this->value_.isNull() && !this->additional_data_.isNull()) {
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
error_object["data"] = this->additional_data_;
}
json_object["value"] = error_object;
} else {
json_object["value"] = this->value_;
}
Updating JsonCpp library to latest This is to resolve issues with creating a JSON value that contains the empty string. Fixes issue #5664.
2018-03-22 13:55:29 -07:00
Json::StreamWriterBuilder writer;
std::string output(Json::writeString(writer, json_object));
KristianRosenvold: Removed windows carriage returns
2013-01-11 22:18:32 +01:00
return output;
}
void Response::SetSuccessResponse(const Json::Value& response_value) {
LOG(TRACE) << "Entering Response::SetSuccessResponse";
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
this->SetResponse("", response_value);
KristianRosenvold: Removed windows carriage returns
2013-01-11 22:18:32 +01:00
}
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
void Response::SetResponse(const std::string& error,
const Json::Value& response_value) {
KristianRosenvold: Removed windows carriage returns
2013-01-11 22:18:32 +01:00
LOG(TRACE) << "Entering Response::SetResponse";
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
this->error_ = error;
KristianRosenvold: Removed windows carriage returns
2013-01-11 22:18:32 +01:00
this->value_ = response_value;
}
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
void Response::SetErrorResponse(const std::string& error,
const std::string& message) {
LOG(TRACE) << "Entering Response::SetErrorResponse";
this->SetResponse(error, message);
}
KristianRosenvold: Removed windows carriage returns
2013-01-11 22:18:32 +01:00
void Response::SetErrorResponse(const int status_code,
const std::string& message) {
LOG(TRACE) << "Entering Response::SetErrorResponse";
LOG(WARN) << "Error response has status code " << status_code << " and message '" << message << "' message";
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
this->SetErrorResponse(ConvertErrorCode(status_code), message);
}
void Response::AddAdditionalData(const std::string& data_name,
const std::string& data_value) {
LOG(TRACE) << "Entering Response::AddAdditionalData";
if (this->additional_data_.isNull()) {
Json::Value new_data;
this->additional_data_ = new_data;
}
this->additional_data_[data_name] = data_value;
KristianRosenvold: Removed windows carriage returns
2013-01-11 22:18:32 +01:00
}
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
std::string Response::GetSessionId(void) {
if (this->error_.size() == 0) {
return this->value_.get("sessionId", "").asString();
}
return "";
}
int Response::GetHttpResponseCode(void) {
int response_code = 200;
if (this->error_ == ERROR_ELEMENT_CLICK_INTERCEPTED ||
this->error_ == ERROR_ELEMENT_NOT_SELECTABLE ||
this->error_ == ERROR_ELEMENT_NOT_INTERACTABLE ||
this->error_ == ERROR_INSECURE_CERTIFICATE ||
this->error_ == ERROR_INVALID_ARGUMENT ||
this->error_ == ERROR_INVALID_COOKIE_DOMAIN ||
this->error_ == ERROR_INVALID_COORDINATES ||
this->error_ == ERROR_INVALID_ELEMENT_STATE ||
Updating IE driver HTTP response code for stale elements
2017-11-26 11:53:30 -08:00
this->error_ == ERROR_INVALID_SELECTOR) {
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
response_code = 400;
} else if (this->error_ == ERROR_INVALID_SESSION_ID ||
this->error_ == ERROR_NO_SUCH_COOKIE ||
Updating HTTP error return status for IE driver to align with spec
2017-10-18 11:52:05 -07:00
this->error_ == ERROR_NO_SUCH_ALERT ||
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
this->error_ == ERROR_NO_SUCH_ELEMENT ||
Updating HTTP error return status for IE driver to align with spec
2017-10-18 11:52:05 -07:00
this->error_ == ERROR_NO_SUCH_FRAME ||
this->error_ == ERROR_NO_SUCH_WINDOW ||
Updating IE driver HTTP response code for stale elements
2017-11-26 11:53:30 -08:00
this->error_ == ERROR_STALE_ELEMENT_REFERENCE ||
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
this->error_ == ERROR_UNKNOWN_COMMAND) {
response_code = 404;
} else if (this->error_ == ERROR_UNKNOWN_METHOD) {
response_code = 405;
} else if (this->error_ == ERROR_JAVASCRIPT_ERROR ||
this->error_ == ERROR_MOVE_TARGET_OUT_OF_BOUNDS ||
Updating IE to return 500 for timeouts instead of 408 Some HTTP clients would retry when receiving a 408 status code. Switching to 500 resolves that issue.
2018-08-31 08:10:41 -07:00
this->error_ == ERROR_SCRIPT_TIMEOUT ||
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
this->error_ == ERROR_SESSION_NOT_CREATED ||
this->error_ == ERROR_UNABLE_TO_SET_COOKIE ||
this->error_ == ERROR_UNABLE_TO_CAPTURE_SCREEN ||
this->error_ == ERROR_UNEXPECTED_ALERT_OPEN ||
Updating IE to return 500 for timeouts instead of 408 Some HTTP clients would retry when receiving a 408 status code. Switching to 500 resolves that issue.
2018-08-31 08:10:41 -07:00
this->error_ == ERROR_UNKNOWN_ERROR ||
Updating IE to be able to close Windows 10 credentials dialog When Microsoft updated Windows 10's credentials prompt dialog, they made it a dialog that is not a standard alert dialog and therefore not able to be automated using standard Windows automation techniques. With a recent preview release, it became possible to manipulate this dialog using the UI Automation feature of Windows. The driver will now be able to accept or dismiss this credentials dialog now. Please note that there is still no supported solution for entering credentials, as there is no support for that feature in the W3C WebDriver Specification.
2019-02-25 11:33:54 -08:00
this->error_ == ERROR_UNSUPPORTED_OPERATION ||
Updating IE to return 500 for timeouts instead of 408 Some HTTP clients would retry when receiving a 408 status code. Switching to 500 resolves that issue.
2018-08-31 08:10:41 -07:00
this->error_ == ERROR_WEBDRIVER_TIMEOUT) {
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
response_code = 500;
} else {
response_code = 200;
}
return response_code;
}
std::string Response::ConvertErrorCode(const int error_code) {
if (error_code == WD_SUCCESS) {
return "";
} else if (error_code == ENOSUCHFRAME) {
return ERROR_NO_SUCH_FRAME;
} else if (error_code == ENOSUCHWINDOW) {
return ERROR_NO_SUCH_WINDOW;
} else if (error_code == EOBSOLETEELEMENT) {
return ERROR_STALE_ELEMENT_REFERENCE;
} else if (error_code == EINVALIDSELECTOR) {
return ERROR_INVALID_SELECTOR;
} else if (error_code == ENOSUCHALERT) {
return ERROR_NO_SUCH_ALERT;
} else if (error_code == EUNEXPECTEDALERTOPEN) {
return ERROR_UNEXPECTED_ALERT_OPEN;
} else if (error_code == ENOSUCHCOOKIE) {
return ERROR_NO_SUCH_COOKIE;
} else if (error_code == EELEMENTNOTENABLED) {
return ERROR_INVALID_ELEMENT_STATE;
} else if (error_code == EELEMENTNOTDISPLAYED) {
return ERROR_ELEMENT_NOT_INTERACTABLE;
} else if (error_code == EUNEXPECTEDJSERROR) {
return ERROR_JAVASCRIPT_ERROR;
} else if (error_code == EINVALIDCOOKIEDOMAIN) {
return ERROR_INVALID_COOKIE_DOMAIN;
} else if (error_code == ESCRIPTTIMEOUT) {
return ERROR_SCRIPT_TIMEOUT;
Modifying mouse event handling to match W3C Specification THIS IS A POTENTIAL BREAKING CHANGE. The simulation of mouse movement for the actions command now conforms to the W3C WebDriver Specification for mouse movement. This means that offsets in elements are now measured from the center of the element instead of the top-left, which was the previous behavior. Additionally, attempting to move the mouse pointer outside the browser view port will result in a "mouse movement out of bounds" error. While users should be aware that this might cause code using user interactions to fail, not that the behavior is now consistent with the behavior outlined in the specification, and the behavior of geckodriver in particular.
2018-02-23 13:55:26 -08:00
} else if (error_code == EMOVETARGETOUTOFBOUNDS) {
return ERROR_MOVE_TARGET_OUT_OF_BOUNDS;
Throw an error for key actions taking multiple characters in IE The key actions as defined by the W3C WebDriver Specification take a JSON payload that requires the resulting key for the key down or key up action to resolve to a single Unicode code point or a single grapheme cluster (what appears to be a single logical "character" from a user's perspective). The IE driver will now evaluate the item passed into the key down or key up action, and, taking combining characters into account, attempts to make sure there is only a single grapheme present, if more than one Unicode code point is sent. If the entered string would results in multiple grapheme clusters, the driver now returns an invalid argument error, as per the spec.
2018-05-01 13:02:45 -07:00
} else if (error_code == EINVALIDARGUMENT) {
return ERROR_INVALID_ARGUMENT;
Correcting error statuses returned for switching frames in IE The IE driver now returns the correct status as specified by the W3C WebDriver Specification for error conditions encountered when attempting to switch frames.
2019-01-22 16:44:28 -08:00
} else if (error_code == ENOSUCHELEMENT) {
return ERROR_NO_SUCH_ELEMENT;
Updating IE to be able to close Windows 10 credentials dialog When Microsoft updated Windows 10's credentials prompt dialog, they made it a dialog that is not a standard alert dialog and therefore not able to be automated using standard Windows automation techniques. With a recent preview release, it became possible to manipulate this dialog using the UI Automation feature of Windows. The driver will now be able to accept or dismiss this credentials dialog now. Please note that there is still no supported solution for entering credentials, as there is no support for that feature in the W3C WebDriver Specification.
2019-02-25 11:33:54 -08:00
} else if (error_code == EUNSUPPORTEDOPERATION) {
return ERROR_UNSUPPORTED_OPERATION;
Implementing W3C Specificiation compliance for IE driver This commit adds the remote protocol end points and handling of commands as required by the W3C WebDriver Specification for the IE driver. It deprecates and mostly removes behavior that is at odds with the specification, but may have been the proper behavior under the open-source dialect of the protocol. Issues arising from this version of the driver that appeared to work in previous versions will only be addressed if a simple test case is provided that demonstrates it working in a prior version of the driver and failing in this one. Reported issues lacking such a test case will be summarily closed.
2017-02-22 14:13:25 -08:00
}
return "";
Make IE driver directly return capabilities from new session command Previously, the driver would return a redirect HTTP response (303), and the language bindings were expected to follow the redirect to get the returned capabilities. This has been an obsolete pattern for some time, and the IE driver is only now conforming to the proper pattern of simply returning a 200 response with the correct capabilities as part of the body.
2016-02-18 12:09:31 -08:00
}
Integrating the Microsoft Internet Explorer driver implementation This commit optionally allows the user to use the Microsoft-supplied implementation of WebDriver for IE 11 and above. To use the Microsoft implementation, the user must have the August 2014 updates to Internet Explorer installed through Windows Update, and must install the IE Web Driver Tool for Internet Explorer 11 download from Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=44069). Once those prerequisites are installed, the user can use the InternetExplorerDriverService object in the language bindings to set the implementation to be used. By default, the driver will continue to use the driver implementation developed by the open-source project. Over time as the Microsoft implementation matures, this will be switched to use that implementation, first by default, then exclusively.
2014-09-05 02:00:00 +00:00
// TODO: This method will be rendered unnecessary once all implementations
// move to string status codes instead of integer status codes. This mapping
// is not entirely correct; it's merely intended as a stopgap.
int Response::ConvertStatusToCode(const std::string& status_string) {
if (status_string == "success") {
// Special case success to return early.
return WD_SUCCESS;
}
if (status_string == "element not selectable") {
return EELEMENTNOTSELECTED;
}
if (status_string == "element not visible") {
return EELEMENTNOTDISPLAYED;
}
if (status_string == "invalid cookie domain") {
return EINVALIDCOOKIEDOMAIN;
}
if (status_string == "invalid element coordinates") {
return EINVALIDCOORDINATES;
}
if (status_string == "invalid element state") {
return EELEMENTNOTENABLED;
}
if (status_string == "invalid selector") {
return EINVALIDSELECTOR;
}
if (status_string == "javascript error") {
return EUNEXPECTEDJSERROR;
}
if (status_string == "no such alert") {
Enabling handling of authentication dialogs in IE driver
2015-07-14 14:52:52 -04:00
return ENOSUCHALERT;
Integrating the Microsoft Internet Explorer driver implementation This commit optionally allows the user to use the Microsoft-supplied implementation of WebDriver for IE 11 and above. To use the Microsoft implementation, the user must have the August 2014 updates to Internet Explorer installed through Windows Update, and must install the IE Web Driver Tool for Internet Explorer 11 download from Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=44069). Once those prerequisites are installed, the user can use the InternetExplorerDriverService object in the language bindings to set the implementation to be used. By default, the driver will continue to use the driver implementation developed by the open-source project. Over time as the Microsoft implementation matures, this will be switched to use that implementation, first by default, then exclusively.
2014-09-05 02:00:00 +00:00
}
if (status_string == "no such element") {
return ENOSUCHELEMENT;
}
if (status_string == "no such frame") {
return ENOSUCHFRAME;
}
if (status_string == "no such window") {
return ENOSUCHWINDOW;
}
if (status_string == "script timeout") {
return ESCRIPTTIMEOUT;
}
if (status_string == "stale element reference") {
return EOBSOLETEELEMENT;
}
if (status_string == "timeout") {
return ETIMEOUT;
}
if (status_string == "unable to set cookie") {
return EUNABLETOSETCOOKIE;
}
if (status_string == "unexpected alert open") {
Enabling handling of authentication dialogs in IE driver
2015-07-14 14:52:52 -04:00
return EUNEXPECTEDALERTOPEN;
Integrating the Microsoft Internet Explorer driver implementation This commit optionally allows the user to use the Microsoft-supplied implementation of WebDriver for IE 11 and above. To use the Microsoft implementation, the user must have the August 2014 updates to Internet Explorer installed through Windows Update, and must install the IE Web Driver Tool for Internet Explorer 11 download from Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=44069). Once those prerequisites are installed, the user can use the InternetExplorerDriverService object in the language bindings to set the implementation to be used. By default, the driver will continue to use the driver implementation developed by the open-source project. Over time as the Microsoft implementation matures, this will be switched to use that implementation, first by default, then exclusively.
2014-09-05 02:00:00 +00:00
}
if (status_string == "unknown command") {
return ENOTIMPLEMENTED;
}
if (status_string == "unknown error") {
return EUNHANDLEDERROR;
}
Updating IE to be able to close Windows 10 credentials dialog When Microsoft updated Windows 10's credentials prompt dialog, they made it a dialog that is not a standard alert dialog and therefore not able to be automated using standard Windows automation techniques. With a recent preview release, it became possible to manipulate this dialog using the UI Automation feature of Windows. The driver will now be able to accept or dismiss this credentials dialog now. Please note that there is still no supported solution for entering credentials, as there is no support for that feature in the W3C WebDriver Specification.
2019-02-25 11:33:54 -08:00
if (status_string == "unsupported operation") {
return EUNSUPPORTEDOPERATION;
}
Integrating the Microsoft Internet Explorer driver implementation This commit optionally allows the user to use the Microsoft-supplied implementation of WebDriver for IE 11 and above. To use the Microsoft implementation, the user must have the August 2014 updates to Internet Explorer installed through Windows Update, and must install the IE Web Driver Tool for Internet Explorer 11 download from Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=44069). Once those prerequisites are installed, the user can use the InternetExplorerDriverService object in the language bindings to set the implementation to be used. By default, the driver will continue to use the driver implementation developed by the open-source project. Over time as the Microsoft implementation matures, this will be switched to use that implementation, first by default, then exclusively.
2014-09-05 02:00:00 +00:00
return EUNHANDLEDERROR;
}
KristianRosenvold: Removed windows carriage returns
2013-01-11 22:18:32 +01:00
} // namespace webdriver
Reference in New Issue Copy Permalink