MORPH
SIGN IN SIGN UP
SeleniumHQ / selenium UNCLAIMED

A browser automation framework and ecosystem.

34168 0 84 Java
Normal View History Raw
Update copyright notices for the javascript/ tree for #401. I still need to update selenium-core - lots of files in there that need manual review.
2015-04-04 09:53:59 -07: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"); you may not use this file except in compliance
// with the License. You may obtain a copy of the License at
Roll back addition of @license tag to all JS files. This bloats the atoms considerably with no benefit.
2014-11-12 19:33:37 +00:00
//
Update copyright notices for the javascript/ tree for #401. I still need to update selenium-core - lots of files in there that need manual review.
2015-04-04 09:53:59 -07:00
// http://www.apache.org/licenses/LICENSE-2.0
Roll back addition of @license tag to all JS files. This bloats the atoms considerably with no benefit.
2014-11-12 19:33:37 +00:00
//
Update copyright notices for the javascript/ tree for #401. I still need to update selenium-core - lots of files in there that need manual review.
2015-04-04 09:53:59 -07:00
// 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.
SimonStewart (on behalf of Googlers): Updates to the atoms, including adding touch emulation r13781
2011-09-08 14:00:21 +00:00
/**
* @fileoverview The file contains an abstraction of a touch screen
* for simulating atomic touchscreen actions.
*/
goog.provide('bot.Touchscreen');
goog.require('bot');
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
goog.require('bot.Device');
goog.require('bot.Error');
goog.require('bot.ErrorCode');
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
goog.require('bot.dom');
[bazel] Bump `rules_closure` and google closure libary to latest release (#16755) * [bazel] Bump `rules_closure` and google closure libary to latest release The Google Closure Library is the last public release, and it seems unlikely we'll ever update it again. The new version of `rules_closure` brings a new version of the closure compiler. This is stricter than the previous compiler, and necessitated an update of the Google Closure Library. However, this new version of the library had removed some key functions we relied upon. We've had to rework both our own code and the vendored version of closure to get it to work with the latest closure compiler. * cp: set a flag to allow protobuf to compile on windows * cp: use a wrapper to avoid line length issues on windows
2025-12-20 14:10:39 +00:00
goog.require('bot.events');
goog.require('bot.userAgent');
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
goog.require('goog.dom.TagName');
SimonStewart (on behalf of Googlers): Updates to the atoms, including adding touch emulation r13781
2011-09-08 14:00:21 +00:00
goog.require('goog.math.Coordinate');
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
goog.require('goog.userAgent.product');
[bazel] Bump `rules_closure` and google closure libary to latest release (#16755) * [bazel] Bump `rules_closure` and google closure libary to latest release The Google Closure Library is the last public release, and it seems unlikely we'll ever update it again. The new version of `rules_closure` brings a new version of the closure compiler. This is stricter than the previous compiler, and necessitated an update of the Google Closure Library. However, this new version of the library had removed some key functions we relied upon. We've had to rework both our own code and the vendored version of closure to get it to work with the latest closure compiler. * cp: set a flag to allow protobuf to compile on windows * cp: use a wrapper to avoid line length issues on windows
2025-12-20 14:10:39 +00:00
goog.require('goog.utils');
SimonStewart (on behalf of Googlers): Updates to the atoms, including adding touch emulation r13781
2011-09-08 14:00:21 +00:00
/**
* A TouchScreen that provides atomic touch actions. The metaphor
* for this abstraction is a finger moving above the touchscreen that
* can press and then release the touchscreen when specified.
*
* The touchscreen supports three actions: press, release, and move.
*
* @constructor
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
* @extends {bot.Device}
SimonStewart (on behalf of Googlers): Updates to the atoms, including adding touch emulation r13781
2011-09-08 14:00:21 +00:00
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen = function () {
[bazel] Bump `rules_closure` and google closure libary to latest release (#16755) * [bazel] Bump `rules_closure` and google closure libary to latest release The Google Closure Library is the last public release, and it seems unlikely we'll ever update it again. The new version of `rules_closure` brings a new version of the closure compiler. This is stricter than the previous compiler, and necessitated an update of the Google Closure Library. However, this new version of the library had removed some key functions we relied upon. We've had to rework both our own code and the vendored version of closure to get it to work with the latest closure compiler. * cp: set a flag to allow protobuf to compile on windows * cp: use a wrapper to avoid line length issues on windows
2025-12-20 14:10:39 +00:00
bot.Device.call(this);
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
The new Closure compiler allows you collapse @type and @private annotations: /** * @type {string} * @private */ var foo = ''; /** @private {string} */ var bar = ''; Remove some clutter from our code base by applying this abbreviated syntax throughout. There should be no functional changes.
2013-03-10 13:56:37 -07:00
/** @private {!goog.math.Coordinate} */
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
this.clientXY_ = new goog.math.Coordinate(0, 0);
The new Closure compiler allows you collapse @type and @private annotations: /** * @type {string} * @private */ var foo = ''; /** @private {string} */ var bar = ''; Remove some clutter from our code base by applying this abbreviated syntax throughout. There should be no functional changes.
2013-03-10 13:56:37 -07:00
/** @private {!goog.math.Coordinate} */
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
this.clientXY2_ = new goog.math.Coordinate(0, 0);
SimonStewart (on behalf of Googlers): Updates to the atoms, including adding touch emulation r13781
2011-09-08 14:00:21 +00:00
};
[bazel] Bump `rules_closure` and google closure libary to latest release (#16755) * [bazel] Bump `rules_closure` and google closure libary to latest release The Google Closure Library is the last public release, and it seems unlikely we'll ever update it again. The new version of `rules_closure` brings a new version of the closure compiler. This is stricter than the previous compiler, and necessitated an update of the Google Closure Library. However, this new version of the library had removed some key functions we relied upon. We've had to rework both our own code and the vendored version of closure to get it to work with the latest closure compiler. * cp: set a flag to allow protobuf to compile on windows * cp: use a wrapper to avoid line length issues on windows
2025-12-20 14:10:39 +00:00
goog.utils.inherits(bot.Touchscreen, bot.Device);
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
The new Closure compiler allows you collapse @type and @private annotations: /** * @type {string} * @private */ var foo = ''; /** @private {string} */ var bar = ''; Remove some clutter from our code base by applying this abbreviated syntax throughout. There should be no functional changes.
2013-03-10 13:56:37 -07:00
/** @private {boolean} */
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
bot.Touchscreen.prototype.fireMouseEventsOnRelease_ = true;
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
/** @private {boolean} */
bot.Touchscreen.prototype.cancelled_ = false;
The new Closure compiler allows you collapse @type and @private annotations: /** * @type {string} * @private */ var foo = ''; /** @private {string} */ var bar = ''; Remove some clutter from our code base by applying this abbreviated syntax throughout. There should be no functional changes.
2013-03-10 13:56:37 -07:00
/** @private {number} */
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
bot.Touchscreen.prototype.touchIdentifier_ = 0;
The new Closure compiler allows you collapse @type and @private annotations: /** * @type {string} * @private */ var foo = ''; /** @private {string} */ var bar = ''; Remove some clutter from our code base by applying this abbreviated syntax throughout. There should be no functional changes.
2013-03-10 13:56:37 -07:00
/** @private {number} */
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
bot.Touchscreen.prototype.touchIdentifier2_ = 0;
The new Closure compiler allows you collapse @type and @private annotations: /** * @type {string} * @private */ var foo = ''; /** @private {string} */ var bar = ''; Remove some clutter from our code base by applying this abbreviated syntax throughout. There should be no functional changes.
2013-03-10 13:56:37 -07:00
/** @private {number} */
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
bot.Touchscreen.prototype.touchCounter_ = 2;
SimonStewart (on behalf of Googlers): Updates to the atoms, including adding touch emulation r13781
2011-09-08 14:00:21 +00:00
/**
* Press the touch screen. Pressing before moving results in an exception.
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
* Pressing while already pressed also results in an exception.
*
* @param {boolean=} opt_press2 Whether or not press the second finger during
* the press. If not defined or false, only the primary finger will be
* pressed.
SimonStewart (on behalf of Googlers): Updates to the atoms, including adding touch emulation r13781
2011-09-08 14:00:21 +00:00
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.prototype.press = function (opt_press2) {
DanielWagnerHall on behalf of AGoogler: Address a TODO in the code by add a touch event firing method to the device class and factoring out the code in touchscreen.js. r15917
2012-02-19 20:32:56 +00:00
if (this.isPressed()) {
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
throw new bot.Error(bot.ErrorCode.UNKNOWN_ERROR,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
'Cannot press touchscreen when already pressed.');
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
}
this.touchIdentifier_ = this.touchCounter_++;
if (opt_press2) {
this.touchIdentifier2_ = this.touchCounter_++;
}
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
if (bot.userAgent.IE_DOC_10) {
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
this.fireMouseEventsOnRelease_ = true;
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
this.firePointerEvents_(bot.Touchscreen.fireSinglePressPointer_);
} else {
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
this.fireMouseEventsOnRelease_ = this.fireTouchEvent_(
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.events.EventType.TOUCHSTART);
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
}
SimonStewart (on behalf of Googlers): Updates to the atoms, including adding touch emulation r13781
2011-09-08 14:00:21 +00:00
};
/**
* Releases an element on a touchscreen. Releasing an element that is not
* pressed results in an exception.
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.prototype.release = function () {
DanielWagnerHall on behalf of AGoogler: Address a TODO in the code by add a touch event firing method to the device class and factoring out the code in touchscreen.js. r15917
2012-02-19 20:32:56 +00:00
if (!this.isPressed()) {
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
throw new bot.Error(bot.ErrorCode.UNKNOWN_ERROR,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
'Cannot release touchscreen when not already pressed.');
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
}
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
if (!bot.userAgent.IE_DOC_10) {
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
this.fireTouchReleaseEvents_();
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
} else if (!this.cancelled_) {
this.firePointerEvents_(bot.Touchscreen.fireSingleReleasePointer_);
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
}
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
bot.Device.clearPointerMap();
DanielWagnerHall on behalf of AGoogler: Address a TODO in the code by add a touch event firing method to the device class and factoring out the code in touchscreen.js. r15917
2012-02-19 20:32:56 +00:00
this.touchIdentifier_ = 0;
this.touchIdentifier2_ = 0;
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
this.cancelled_ = false;
SimonStewart (on behalf of Googlers): Updates to the atoms, including adding touch emulation r13781
2011-09-08 14:00:21 +00:00
};
/**
* Moves finger along the touchscreen.
*
* @param {!Element} element Element that is being pressed.
* @param {!goog.math.Coordinate} coords Coordinates relative to
* currentElement.
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
* @param {goog.math.Coordinate=} opt_coords2 Coordinates relative to
* currentElement.
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.prototype.move = function (element, coords, opt_coords2) {
DanielWagnerHall on behalf of AGoogler: Address a TODO in the code by add a touch event firing method to the device class and factoring out the code in touchscreen.js. r15917
2012-02-19 20:32:56 +00:00
// The target element for touch actions is the original element. Hence, the
// element is set only when the touchscreen is not currently being pressed.
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
// The exception is IE10 which fire events on the moved to element.
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
var originalElement = this.getElement();
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
if (!this.isPressed() || bot.userAgent.IE_DOC_10) {
DanielWagnerHall on behalf of AGoogler: Address a TODO in the code by add a touch event firing method to the device class and factoring out the code in touchscreen.js. r15917
2012-02-19 20:32:56 +00:00
this.setElement(element);
}
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
var rect = bot.dom.getClientRect(element);
this.clientXY_.x = coords.x + rect.left;
this.clientXY_.y = coords.y + rect.top;
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
[bazel] Bump `rules_closure` and google closure libary to latest release (#16755) * [bazel] Bump `rules_closure` and google closure libary to latest release The Google Closure Library is the last public release, and it seems unlikely we'll ever update it again. The new version of `rules_closure` brings a new version of the closure compiler. This is stricter than the previous compiler, and necessitated an update of the Google Closure Library. However, this new version of the library had removed some key functions we relied upon. We've had to rework both our own code and the vendored version of closure to get it to work with the latest closure compiler. * cp: set a flag to allow protobuf to compile on windows * cp: use a wrapper to avoid line length issues on windows
2025-12-20 14:10:39 +00:00
if (opt_coords2 !== undefined) {
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
this.clientXY2_.x = opt_coords2.x + rect.left;
this.clientXY2_.y = opt_coords2.y + rect.top;
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
}
DanielWagnerHall on behalf of AGoogler: Address a TODO in the code by add a touch event firing method to the device class and factoring out the code in touchscreen.js. r15917
2012-02-19 20:32:56 +00:00
if (this.isPressed()) {
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
if (!bot.userAgent.IE_DOC_10) {
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
this.fireMouseEventsOnRelease_ = false;
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
this.fireTouchEvent_(bot.events.EventType.TOUCHMOVE);
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
} else if (!this.cancelled_) {
if (element != originalElement) {
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
this.fireMouseEventsOnRelease_ = false;
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
}
if (bot.Touchscreen.hasMsTouchActionsEnabled_(element)) {
this.firePointerEvents_(bot.Touchscreen.fireSingleMovePointer_);
} else {
this.fireMSPointerEvent(bot.events.EventType.MSPOINTEROUT, coords, -1,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
this.touchIdentifier_, MSPointerEvent.MSPOINTER_TYPE_TOUCH, true);
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
this.fireMouseEvent(bot.events.EventType.MOUSEOUT, coords, 0);
this.fireMSPointerEvent(bot.events.EventType.MSPOINTERCANCEL, coords, 0,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
this.touchIdentifier_, MSPointerEvent.MSPOINTER_TYPE_TOUCH, true);
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
this.cancelled_ = true;
bot.Device.clearPointerMap();
}
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
}
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
}
};
/**
* Returns whether the touchscreen is currently pressed.
*
* @return {boolean} Whether the touchscreen is pressed.
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.prototype.isPressed = function () {
DanielWagnerHall on behalf of AGoogler: Address a TODO in the code by add a touch event firing method to the device class and factoring out the code in touchscreen.js. r15917
2012-02-19 20:32:56 +00:00
return !!this.touchIdentifier_;
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
};
/**
* A helper function to fire touch events.
*
[bazel] Bump `rules_closure` and google closure libary to latest release (#16755) * [bazel] Bump `rules_closure` and google closure libary to latest release The Google Closure Library is the last public release, and it seems unlikely we'll ever update it again. The new version of `rules_closure` brings a new version of the closure compiler. This is stricter than the previous compiler, and necessitated an update of the Google Closure Library. However, this new version of the library had removed some key functions we relied upon. We've had to rework both our own code and the vendored version of closure to get it to work with the latest closure compiler. * cp: set a flag to allow protobuf to compile on windows * cp: use a wrapper to avoid line length issues on windows
2025-12-20 14:10:39 +00:00
* @param {!bot.events.EventFactory_} type Event type.
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
* @return {boolean} Whether the event fired successfully or was cancelled.
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
* @private
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.prototype.fireTouchEvent_ = function (type) {
DanielWagnerHall on behalf of AGoogler: Address a TODO in the code by add a touch event firing method to the device class and factoring out the code in touchscreen.js. r15917
2012-02-19 20:32:56 +00:00
if (!this.isPressed()) {
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
throw new bot.Error(bot.ErrorCode.UNKNOWN_ERROR,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
'Should never fire event when touchscreen is not pressed.');
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
}
DanielWagnerHall on behalf of AGoogler: Address a TODO in the code by add a touch event firing method to the device class and factoring out the code in touchscreen.js. r15917
2012-02-19 20:32:56 +00:00
var touchIdentifier2;
var coords2;
if (this.touchIdentifier2_) {
touchIdentifier2 = this.touchIdentifier2_;
coords2 = this.clientXY2_;
SimonStewart on behalf of numerous Googlers: Updating the atoms. This introduces a device abstraction which is used by a mouse and keyboard class when simulating events. This should also continue to resolve the horror that is #2700. Tested on Firefox. IE next. r15055
2011-12-06 11:44:44 +00:00
}
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
return this.fireTouchEvent(type, this.touchIdentifier_, this.clientXY_,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
touchIdentifier2, coords2);
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
};
/**
* A helper function to fire touch events that occur on a release.
*
* @private
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.prototype.fireTouchReleaseEvents_ = function () {
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
var touchendSuccess = this.fireTouchEvent_(bot.events.EventType.TOUCHEND);
// In general, TouchScreen.Release will fire the legacy mouse events:
// mousemove, mousedown, mouseup, and click after the touch events have been
// fired. The click button should be zero and only one mousemove should fire.
// Under the following cases, mouse events should not be fired:
// 1. Movement has occurred since press.
// 2. Any event handler for touchstart has called preventDefault().
// 3. Any event handler for touchend has called preventDefault(), and browser
// is Mobile Safari or Chrome.
var fireMouseEvents =
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
this.fireMouseEventsOnRelease_ &&
(touchendSuccess || !(bot.userAgent.IOS ||
goog.userAgent.product.CHROME));
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
if (fireMouseEvents) {
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
this.fireMouseEvent(bot.events.EventType.MOUSEMOVE, this.clientXY_, 0);
var performFocus = this.fireMouseEvent(bot.events.EventType.MOUSEDOWN,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
this.clientXY_, 0);
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
// Element gets focus after the mousedown event only if the mousedown was
// not cancelled.
if (performFocus) {
this.focusOnElement();
}
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
this.maybeToggleOption();
Always send a click event when a mouseup event would complete a click. Before this, if a mouseup handler caused the target element to become non-interactable, we would abort and not send a click event. The W3C spec says that "A click is defined as a mousedown and mouseup over the same screen location." Once the mouseup has occurred, the click has also occurred, so we are obligated to produce the click event even if a mouseup handler causes the element becomes non-interactable. This is also consistent with the real-world behavior of Chrome, Firefox, IE8, IE11, Safari 8, and the Android stock browser on Jellybean. -- On behalf of juangj.
2015-02-24 23:55:39 -08:00
// If a mouseup event is dispatched to an interactable event, and that
// mouseup would complete a click, then the click event must be dispatched
// even if the element becomes non-interactable after the mouseup.
var elementInteractableBeforeMouseup =
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.dom.isInteractable(this.getElement());
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
this.fireMouseEvent(bot.events.EventType.MOUSEUP, this.clientXY_, 0);
// Special click logic to follow links and to perform form actions.
Do not issue click for option elements on Windows Phone
2013-10-09 12:50:50 -04:00
if (!(bot.userAgent.WINDOWS_PHONE &&
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.dom.isElement(this.getElement(), goog.dom.TagName.OPTION))) {
this.clickElement(this.clientXY_,
Always send a click event when a mouseup event would complete a click. Before this, if a mouseup handler caused the target element to become non-interactable, we would abort and not send a click event. The W3C spec says that "A click is defined as a mousedown and mouseup over the same screen location." Once the mouseup has occurred, the click has also occurred, so we are obligated to produce the click event even if a mouseup handler causes the element becomes non-interactable. This is also consistent with the real-world behavior of Chrome, Firefox, IE8, IE11, Safari 8, and the Android stock browser on Jellybean. -- On behalf of juangj.
2015-02-24 23:55:39 -08:00
/* button */ 0,
/* opt_force */ elementInteractableBeforeMouseup);
Do not issue click for option elements on Windows Phone
2013-10-09 12:50:50 -04:00
}
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
}
};
/**
* A helper function to fire a sequence of Pointer events.
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
* @param {function(!bot.Touchscreen, !Element, !goog.math.Coordinate, number,
* boolean)} fireSinglePointer A function that fires a set of events for one
* finger.
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
* @private
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.prototype.firePointerEvents_ = function (fireSinglePointer) {
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
fireSinglePointer(this, this.getElement(), this.clientXY_,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
this.touchIdentifier_, true);
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
if (this.touchIdentifier2_ &&
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.hasMsTouchActionsEnabled_(this.getElement())) {
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
fireSinglePointer(this, this.getElement(),
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
this.clientXY2_, this.touchIdentifier2_, false);
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
}
};
/**
* A helper function to fire Pointer events related to a press.
*
* @param {!bot.Touchscreen} ts A touchscreen object.
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
* @param {!Element} element Element that is being pressed.
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
* @param {!goog.math.Coordinate} coords Coordinates relative to
* currentElement.
* @param {number} id The touch identifier.
* @param {boolean} isPrimary Whether the pointer represents the primary point
* of contact.
* @private
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.fireSinglePressPointer_ = function (ts, element, coords, id,
isPrimary) {
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
// Fire a mousemove event.
ts.fireMouseEvent(bot.events.EventType.MOUSEMOVE, coords, 0);
// Fire a MSPointerOver and mouseover events.
ts.fireMSPointerEvent(bot.events.EventType.MSPOINTEROVER, coords, 0, id,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
MSPointerEvent.MSPOINTER_TYPE_TOUCH, isPrimary);
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
ts.fireMouseEvent(bot.events.EventType.MOUSEOVER, coords, 0);
// Fire a MSPointerDown and mousedown events.
ts.fireMSPointerEvent(bot.events.EventType.MSPOINTERDOWN, coords, 0, id,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
MSPointerEvent.MSPOINTER_TYPE_TOUCH, isPrimary);
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
// Element gets focus after the mousedown event.
if (ts.fireMouseEvent(bot.events.EventType.MOUSEDOWN, coords, 0)) {
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
// For selectable elements, IE 10 fires a MSGotPointerCapture event.
if (bot.dom.isSelectable(element)) {
ts.fireMSPointerEvent(bot.events.EventType.MSGOTPOINTERCAPTURE, coords, 0,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
id, MSPointerEvent.MSPOINTER_TYPE_TOUCH, isPrimary);
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
}
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
ts.focusOnElement();
}
};
/**
* A helper function to fire Pointer events related to a release.
*
* @param {!bot.Touchscreen} ts A touchscreen object.
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
* @param {!Element} element Element that is being released.
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
* @param {!goog.math.Coordinate} coords Coordinates relative to
* currentElement.
* @param {number} id The touch identifier.
* @param {boolean} isPrimary Whether the pointer represents the primary point
* of contact.
* @private
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.fireSingleReleasePointer_ = function (ts, element, coords, id,
isPrimary) {
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
// Fire a MSPointerUp and mouseup events.
ts.fireMSPointerEvent(bot.events.EventType.MSPOINTERUP, coords, 0, id,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
MSPointerEvent.MSPOINTER_TYPE_TOUCH, isPrimary);
Always send a click event when a mouseup event would complete a click. Before this, if a mouseup handler caused the target element to become non-interactable, we would abort and not send a click event. The W3C spec says that "A click is defined as a mousedown and mouseup over the same screen location." Once the mouseup has occurred, the click has also occurred, so we are obligated to produce the click event even if a mouseup handler causes the element becomes non-interactable. This is also consistent with the real-world behavior of Chrome, Firefox, IE8, IE11, Safari 8, and the Android stock browser on Jellybean. -- On behalf of juangj.
2015-02-24 23:55:39 -08:00
// If a mouseup event is dispatched to an interactable event, and that mouseup
// would complete a click, then the click event must be dispatched even if the
// element becomes non-interactable after the mouseup.
var elementInteractableBeforeMouseup =
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.dom.isInteractable(ts.getElement());
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
ts.fireMouseEvent(bot.events.EventType.MOUSEUP, coords, 0, null, 0, false,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
id);
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
// Fire a click.
Prevent mouse events from firing if touchstart or touchend was canceled. On behalf of Google engineers
2015-06-18 18:58:06 -07:00
if (ts.fireMouseEventsOnRelease_) {
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
ts.maybeToggleOption();
Do not issue click for option elements on Windows Phone
2013-10-09 12:50:50 -04:00
if (!(bot.userAgent.WINDOWS_PHONE &&
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.dom.isElement(element, goog.dom.TagName.OPTION))) {
Always send a click event when a mouseup event would complete a click. Before this, if a mouseup handler caused the target element to become non-interactable, we would abort and not send a click event. The W3C spec says that "A click is defined as a mousedown and mouseup over the same screen location." Once the mouseup has occurred, the click has also occurred, so we are obligated to produce the click event even if a mouseup handler causes the element becomes non-interactable. This is also consistent with the real-world behavior of Chrome, Firefox, IE8, IE11, Safari 8, and the Android stock browser on Jellybean. -- On behalf of juangj.
2015-02-24 23:55:39 -08:00
ts.clickElement(ts.clientXY_,
/* button */ 0,
/* opt_force */ elementInteractableBeforeMouseup,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
id);
Do not issue click for option elements on Windows Phone
2013-10-09 12:50:50 -04:00
}
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
}
if (bot.dom.isSelectable(element)) {
// For selectable elements, IE 10 fires a MSLostPointerCapture event.
ts.fireMSPointerEvent(bot.events.EventType.MSLOSTPOINTERCAPTURE,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
new goog.math.Coordinate(0, 0), 0, id,
MSPointerEvent.MSPOINTER_TYPE_TOUCH, false);
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
}
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
// Fire a MSPointerOut and mouseout events.
ts.fireMSPointerEvent(bot.events.EventType.MSPOINTEROUT, coords, -1, id,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
MSPointerEvent.MSPOINTER_TYPE_TOUCH, isPrimary);
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
ts.fireMouseEvent(bot.events.EventType.MOUSEOUT, coords, 0, null, 0, false,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
id);
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
};
/**
* A helper function to fire Pointer events related to a move.
*
* @param {!bot.Touchscreen} ts A touchscreen object.
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
* @param {!Element} element Element that is being moved.
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
* @param {!goog.math.Coordinate} coords Coordinates relative to
* currentElement.
* @param {number} id The touch identifier.
* @param {boolean} isPrimary Whether the pointer represents the primary point
* of contact.
* @private
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.fireSingleMovePointer_ = function (ts, element, coords, id,
isPrimary) {
DanielWagnerHall on behalf of SeveralGooglers: Pushing out a bunch of Google javascript changes * Added support for new IE10 pointer events * Moved attribute/property conflating from atoms to webdriver atoms * Lots of linting and type fixing * Made bot.action.getInteractableSize public * Added ability to force events to fire on non-interactable elements * Added HTML5 doctype declarations to all test pages * Always use webdriver.atoms.inject not bot.inject, as this is required by the android driver * Updated closure library and compiler to the latest release r18101
2012-11-08 16:22:32 +00:00
// Fire a MSPointerMove and mousemove events.
ts.fireMSPointerEvent(bot.events.EventType.MSPOINTERMOVE, coords, -1, id,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
MSPointerEvent.MSPOINTER_TYPE_TOUCH, isPrimary);
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
ts.fireMouseEvent(bot.events.EventType.MOUSEMOVE, coords, 0, null, 0, false,
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
id);
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
};
/**
* A function that determines whether an element can be manipulated by the user.
* The msTouchAction style is queried and an element can be manipulated if the
* style value is none. If an element cannot be manipulated, then move gestures
* will result in a cancellation and multi-touch events will be prevented. Tap
* gestures will still be allowed. If not on IE 10, the function returns true.
*
* @param {!Element} element The element being manipulated.
* @return {boolean} Whether the element can be manipulated.
* @private
*/
[js] reformat the atoms code, no logical changes
2020-11-27 15:46:30 +00:00
bot.Touchscreen.hasMsTouchActionsEnabled_ = function (element) {
Updating the atoms library on behalf of several Googlers. This update includes support for MS pointer events and refinements to element visibility tests.
2013-06-15 16:19:51 -07:00
if (!bot.userAgent.IE_DOC_10) {
throw new Error('hasMsTouchActionsEnable should only be called from IE 10');
}
// Although this particular element may have a style indicating that it cannot
// receive javascript events, its parent may indicate otherwise.
if (bot.dom.getEffectiveStyle(element, 'ms-touch-action') == 'none') {
return true;
} else {
var parent = bot.dom.getParentElement(element);
return !!parent && bot.Touchscreen.hasMsTouchActionsEnabled_(parent);
}
SimonStewart (on behalf of Googlers): Updates to the atoms, including adding touch emulation r13781
2011-09-08 14:00:21 +00:00
};
Reference in New Issue Copy Permalink