Hi,

Whether RF supports selenium 3.0?

RIDE getting below error:

WebDriverException: Message: Error loading page

for firefix browser.

For reference: when upgrading selenium in cmd displays as below- C:\Users\ethiese>pip install --upgrade selenium Requirement already up-to-date: selenium in c:\python27\lib\site-packages\selenium-3.0.0b2-py2.7.egg

The current Press Key keyword has a severe limitation that pressing special keys like tab requires using escaped ASCII codes like \\09 (double escaping needed because \ itself is an escape character in Robot's data) and not all special keys (e.g. arrows) are supported.

Issue #275 proposed adding support for WebDriver's special keys like ARROR_UP to Press Key and it was implemented by PR #474 in version 1.7.3. Unfortunately this change broke undocumented (and tested) feature inPress Key to allow pressing multiple keys (#489). Such a backwards incompatible change was not considered a good idea, especially in a minor release, and changes were reverted in 1.7.4.

The general consensus in the comments of the aforementioned issues and pull requests tracker and on the Slack channel seems to be the following:

• Adding support for named special keys is an important enhancement.
• It is a good idea to support pressing multiple keys (and Press Key that actually supports it is badly named).
• Press Key behavior should not be changed in backwards incompatible manner.

As a result the consensus seems to be that we want to add new Press Keys keyword that supports named keys. There is no consensus about lower level design decisions, though, but we can discuss about them in the comments of this issue.

With Chrome 44.0.2403, Chrome driver 2.16 Selenium2Library 1.7.2 and selenium 2.46.1 when I use Wait* keywords, the StaleElementReferenceException might occur. Documentation says that keyword should only fail if condition is not met before the timeout, example for Wait Until Page Contains Element keyword, documentation says: Fails if timeout expires before the element appears.

But if StaleElementReferenceException happens, then I see this:

Selenium2Library.Wait Until Element Is Visible xpath=//span/span[text()="${menu_item}"], timeout=5s, error=Menu item ${menu_item} not found on page!
Documentation:  
Waits until element specified with `locator` is visible.
Start / End / Elapsed:  20150730 14:24:49.623 / 20150730 14:24:50.240 / 00:00:00.617
00:00:00.376KEYWORD: common_library_imports.Selenium2library Common Failure
14:24:49.624    TRACE   Arguments: [ u'xpath=//span/span[text()="XXXXXX"]' | timeout=u'5s' | error=u'Menu item XXXXXX not found on page!' ]   
14:24:49.624    DEBUG   POST http://127.0.0.1:55614/session/7f76eac90d05725647286d5bdf089b4a/elements {"using": "xpath", "sessionId": "7f76eac90d05725647286d5bdf089b4a", "value": "//span/span[text()=\"XXXXXX\"]"}   
14:24:49.829    DEBUG   Finished Request    
14:24:49.831    DEBUG   GET http://127.0.0.1:55614/session/7f76eac90d05725647286d5bdf089b4a/element/0.4323001531884074-3/displayed {"sessionId": "7f76eac90d05725647286d5bdf089b4a", "id": "0.4323001531884074-3"}  
14:24:49.855    DEBUG   Finished Request    
14:24:50.239    FAIL    StaleElementReferenceException: Message: stale element reference: element is not attached to the page document
  (Session info: chrome=44.0.2403.125)
  (Driver info: chromedriver=2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf),platform=Windows NT 6.1 SP1 x86_64)
14:24:50.239    DEBUG   Traceback (most recent call last):
  File "<string>", line 2, in wait_until_element_is_visible
  File "C:\Python27\lib\site-packages\Selenium2Library\keywords\keywordgroup.py", line 15, in _run_on_failure_decorator
    return method(*args, **kwargs)
  File "C:\Python27\lib\site-packages\Selenium2Library\keywords\_waiting.py", line 128, in wait_until_element_is_visible
    self._wait_until_no_error(timeout, check_visibility)
  File "C:\Python27\lib\site-packages\Selenium2Library\keywords\_waiting.py", line 237, in _wait_until_no_error
    timeout_error = wait_func(*args)
  File "C:\Python27\lib\site-packages\Selenium2Library\keywords\_waiting.py", line 121, in check_visibility
    visible = self._is_visible(locator)
  File "C:\Python27\lib\site-packages\Selenium2Library\keywords\_element.py", line 723, in _is_visible
    return element.is_displayed()
  File "C:\Python27\lib\site-packages\selenium\webdriver\remote\webelement.py", line 323, in is_displayed
    return self._execute(Command.IS_ELEMENT_DISPLAYED)['value']
  File "C:\Python27\lib\site-packages\selenium\webdriver\remote\webelement.py", line 402, in _execute
    return self._parent.execute(command, params)
  File "C:\Python27\lib\site-packages\Selenium2Library\webdrivermonkeypatches.py", line 11, in execute
    result = self._base_execute(driver_command, params)
  File "C:\Python27\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 175, in execute
    self.error_handler.check_response(response)
  File "C:\Python27\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 166, in check_response
    raise exception_class(message, screen, stacktrace)  
14:24:49.621    TRACE   Arguments: [ ${menu_item}=u'XXXXXX' | ${timeout}=u'10' ]

and keyword did fail immediately. But I did expect that keyword would simply re-try search for the element if the StaleElementReferenceException or any other selenium related error happens before the timeout.

Selenium allows arguments to be passed along with JavaScript that can be referenced in the script using the injected List variable named arguments. Execute Javascript, Execute Async Javascript, and Wait For Condition do not support this feature. This would be useful for passing WebElements and data structures into scripts

When we implement Get Webelement(s), people will naturally want to pass the WebElements as argument(s) to a script. Currently, one can use Assign Id To Element to make a WebElement easy to reference if JS if it is difficult to reference is JS.

Implementing this without breaking test cases or adding keywords would require using keyword arguments for Execute Javascript and Execute Async Javascript. Because they have variable arguments, we cannot add a positional argument. Keyword arguments require RF 2.8 to work.

There is a workaround for this missing functionality on StackOverflow

In some cases i see the "Click Element" keyword had clicked on the element but the action on that element in not triggered. When I say "keyword had clicked on element", it means it did not throw any error. In some cases I can see the dotted border (in screenshot) around the element which normally happens when we click on element. Has anyone encountered such kind of problem?

::My Questions::

1. Can it happen that selenium misses the click
2. I have put the waits for that element to be visible & enable. Assuming a possibility that corresponding JS is not loaded, in this case it should throw error which is not happening. I am capturing details via BrowserMobProxy which does not show any JS error. I am clueless why this is happening.

Few observation:

• Whenever the environment is slow, this tend to happen more
• We tried adding consecutive clicks for same element (with "Run Keyword And Ignore Error" with second "click element") and it worked.

Hi,

I would like to find how to get a matching XPath from the page. I mean I want to pull out all the elements on the page which doesn't have the same xpath but they have a similarity.

Example:

I would like to get all those into a list without hard coding them in my code. So, is there a regex match that I can use here?

hi, on windows 7, Close Browser take more than 1 minute to close the Browser. In fact, the browser is closed very fast but the job take more than 1 mn to terminate the job.

any idea ?

Best regards Bruno

Please review this commit carefully. I wish this keyword was not needed, but I do not see the Selenium team moving all options to a desired capabilities argument anytime soon. This keyword will close many issues people have with using a proxy.

A URL parameter is intentionally omitted because an initial get() is not always appropriate (native app testing w/ Appium).

As is, argument names are not checked through reflection and Python will throw an error like: TypeError: __init__() got an unexpected keyword argument 'bad_arg_name'. Let me know if this is not OK.

possible enancements I can implement if desired: normalizing argument names and/or WebDriver names and matching via reflection. I did not do this because BuiltIn's Call Method does not do this and this keyword is for advanced users.

possible issues: The tests will try and launch Firefox even if you call run_tests with another browser. I tried to test through unit testing, but had problems because the _LoggingKeywords mix-in was not present.

This allows "jquery" and "sizzle" locator prefixes, which delegate to the window's jQuery. Probably not suitable for merging as-is; I think it would be better if jQuery was provided by selenium2library.

But it is easy and probably* works, so I thought I'd share. Maybe it will inspire someone to enhance it.

• I have the change working on a work computer, but due to in-house restrictions, I had to type it in by hand on another computer in order to push to github. The other computer doesn't have robot, so I haven't actually tested the re-typed-in code.... sorry!

What do you guys think about this kind of enhancement: Add a new KW (or extend the Create Webdriver) for attaching to an existing browser/selenium session.

This doesn't make that much sense in "production" environment but would be very useful when implementing test cases. The idea would be to speed-up following scenarios

• When testing web apps there's quite often a scenario where you do lots of stuff and then something breaks: e.g. you have typo in your xpath, a timing issue with (e.g. jQuery not finished) or something else. When this happens you have to start from the beginning but it would be great if you could continue from the point where the TC broke ...
• In environments where the set-up is time consuming, it would great to reuse the browser session(s). For example a set-up where you open a browser and login to the web-app, open another browser and login to the CRM, open yet another browser and login to a web-email app. It would be great to keep those 3 browsers open and skip the browser opening and login steps...

I need this functionality and will implement it for sure, the question is just: should I implement it in my libraries (that use selenium2lib) or should I create a PR for this?

Here a short example how to connect to an existing session:

• Open new browser, print out the session details and leave the browser open

> python sel.py 
c1c31e1e-9b19-4363-9ab7-369e84313601  http://127.0.0.1:55486/hub

• Go manually to google.com with the browser
• re-attach (with session details) and click the I'm feeling lucky button:

> python sel.py c1c31e1e-9b19-4363-9ab7-369e84313601  http://127.0.0.1:55486/hub

sel.py file:

from selenium.webdriver import Firefox, Remote
import sys

def open():
    driver = Firefox()
    print("%s  %s" % (driver.session_id, driver.command_executor._url))
    
def attach(sid, url):
    driver = Remote(command_executor=url, desired_capabilities={})
    driver.session_id = sid
    driver.find_element_by_xpath("//input[contains(@value, 'Lucky')]").click()

sid = sys.argv[1] if len(sys.argv) > 1 else None
url = sys.argv[2] if len(sys.argv) > 2 else None

if sid is None:
    open()
else:
    attach(sid, url)

That I get this exception when using Selenium2Library with the latest Robot Framework code:

Importing test library 'Selenium2Library' failed: ImportError: cannot import name GLOBAL_VARIABLES
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/Selenium2Library/__init__.py", line 2, in <module>
    from keywords import *
  File "/usr/local/lib/python2.7/dist-packages/Selenium2Library/keywords/__init__.py", line 1, in <module>
    from _logging import _LoggingKeywords
  File "/usr/local/lib/python2.7/dist-packages/Selenium2Library/keywords/_logging.py", line 3, in <module>
    from robot.variables import GLOBAL_VARIABLES

Apparently the library uses Robot's internal GLOBAL_VARIABLES that we just we able to remove as part of robotframework/robotframework#532. I don't have time to investigate where and why GLOBAL_VARIABLES are used right now, but I hope the usage could be replaced with something else. I would assume variable related methods in BuiltIn could be used instead. A big benefit of them is that they are part of the public API and thus considered stable.

If it turns out to be hard to fix this on Se2Lib, we can consider adding GLOBAL_VARIABLES back for some time. Our general goal is to get rid of all/most global state like that to make the framework thread safe and easier to parallelize, though.

We have quite a few internal tests for which are tagged as Known Issue under one or another browser. There have also been some recognition of various issues known and tracked within various external organizations (Selenium project or browser WebDriver teams). It would be good if we document any known tickets to our internal tests so that as external issues get resolved we known we can adjust our tests.

This ticket is to look at those processes and see if we can improve upon the current situation.

• Drop Robot Framework 3 and PythonLibCore 2 support, new version of one combined with older version of the other causes type conversion problems.
• Add Firefox to CI runs
• Adjust tests and tags so that they run on Chrome and Firefox

Prerequisites

• I have searched for similar issues in open tickets and cannot find a duplicate. ✅
• The issue still exists against the latest released version of SeleniumLibrary. ✅
• This is not a usage question or support request. For those, see more details in README.rst: https://github.com/robotframework/SeleniumLibrary#support ✅
• You are not using the Java Selenium2Library: https://github.com/MarketSquare/robotframework-seleniumlibrary-java ✅
• Remember that this is a public forum, so remember to remove all sensitive information, like username and password. ✅

For issues

Steps to reproduce the issue

I've created a reproduction here however it's reproducible on any mac when trying to clear text nodes using press keys

Error messages and additional information

It seems that when I use the Selenium keyword press keys to clear a text node, it doesn't work on mac OS. It works fine on Linux & Windows. When I try to use Clear Element Text or Selenium's method .clear(), it doesn't work. I've attached a repository that shows this behavior & highlights the problem I've been seeing. As long as you're on Mac OS, the repository reproduction should show the error I've been dealing with.

Expected behavior and actual behavior

When I follow those steps, I see... The browser seems to press COMMAND+ALT+BACKSPACE but doesn't clear the text

I was expecting...

The browser clears the text but it doesn't

Environment

Browser: Chrome 103 + Browser driver: Chromedriver v107 Operating System: macOS Ventura Libraries

• Robot Framework: 6.0.0
• Selenium: 6.0
• SeleniumLibrary: 6.0
• Interpreter: Python 3.10

Hello,

I have an issue and open two ticket on Selenium and RobotFramework : https://github.com/SeleniumHQ/selenium/issues/10258 https://github.com/robotframework/robotframework/issues/4194

Version installed : Python 3.8

Version of Lib : robotframework 4.1.2
robotframework-appiumlibrary 1.6.3
robotframework-pythonlibcore 3.0.0
robotframework-requests 0.9.2
robotframework-seleniumlibrary 5.1.3
selenium 4.1.0

Selenium grid hub and nodes Version 4.4.0

May I ask you to have a look please ?

Prerequisites

• I have searched for similar issues in open tickets and cannot find a duplicate.
• The issue still exists against the latest released version of SeleniumLibrary.
• This is not a usage question or support request. For those, see more details in README.rst: https://github.com/robotframework/SeleniumLibrary#support
• You are not using the Java Selenium2Library: https://github.com/MarketSquare/robotframework-seleniumlibrary-java
• Remember that this is a public forum, so remember to remove all sensitive information, like username and password.

For issues

Steps to reproduce the issue

Create a simplified example which reproduces the problem. It is good if the example can be run also by us, but this is not always mandatory.

Error messages and additional information

If there is an error, run the test with --loglevel trace set from command line and copy paste the full stack trace to the issue. Use https://gist.github.com/ or similar service for anything that longer than few lines.

Provide other details which might be useful for investigating the issue. Screenshots from application or from unexpected dialogues are example useful. Sometimes showing relevant parts of the log.html is useful too.

Expected behavior and actual behavior

When I follow those steps, I see...

I was expecting...

Environment

Browser: Name and version (Usually available from the about dialogue.) Browser driver: Name and version Operating System: Name and version (Linux, Ubuntu 18.04) Libraries

• Robot Framework: Version
• Selenium: Version
• SeleniumLibrary: Version
• Interpreter: Name and version

Feature requests

Describe the need or the feature you are missing from the SeleniumLibrary. Also it is useful to understand why you need such feature. Many times, it is useful to provide few examples for acceptance tests. Try to avoid technical or implementation details, those will handled later.

This project is not funded by any organisation or company, I do this because I want to do this on my own free time. Therefore if you want feature be implemented, the easiest and usually fastest way usually is to provide pull request. See https://github.com/robotframework/SeleniumLibrary/blob/master/CONTRIBUTING.rst for mode details about project development.

When running under a virtualenv, using python as the interpreter forgets the virtualenv python which executed atest.run.py. Instead using sys.executable which will execute with same interpreter used to execute atest/run.py. I also later check to make sure the interpreter is not None nor an empty string as doc states [1] it may be if "Python is unable to retrieve the interpreter".

Fixes #1796

[1] https://docs.python.org/3.10/library/sys.html#sys.executable