You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
\Facebook\WebDriver\WebDriverPoint::equals compares its own x and y to the integer value of the other x and y, which will always be false in firefox when the position is a float.
$point = new \Facebook\WebDriver\WebDriverPoint(0.0, 0.0);if (!$point->equals($point)) {
throw new LogicException('Point not equals point, but point is the same point! Just making a point here.');
}
Expected behavior
If a point equals a point, it must always be true. Either use $this->x === $other->x or $this->getX() === $other->getX()
Php-webdriver version
1.15.1
PHP version
8.2
How do you start the browser driver or Selenium server
Selenium Hub in Docker Compose with Chrome and Firefox node
Selenium server / Selenium Docker image version
selenium/node-firefox:latest
Browser driver (chromedriver/geckodriver...) version
No response
Browser name and version
Firefox 120.0.1 64bit
Operating system
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Bug description
\Facebook\WebDriver\WebDriverPoint::equals
compares its ownx
andy
to the integer value of the otherx
andy
, which will always be false in firefox when the position is a float.php-webdriver/lib/WebDriverPoint.php
Lines 75 to 79 in 35a8470
How could the issue be reproduced
Expected behavior
If a point equals a point, it must always be true. Either use
$this->x === $other->x
or$this->getX() === $other->getX()
Php-webdriver version
1.15.1
PHP version
8.2
How do you start the browser driver or Selenium server
Selenium Hub in Docker Compose with Chrome and Firefox node
Selenium server / Selenium Docker image version
selenium/node-firefox:latest
Browser driver (chromedriver/geckodriver...) version
No response
Browser name and version
Firefox 120.0.1 64bit
Operating system
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: